Oxide

lp:~osomon/oxide/maxCacheSize

Created by Olivier Tilloy on 2015-03-06 and last modified on 2015-03-11

Only Olivier Tilloy can upload to this branch. If you are Olivier Tilloy please log in for upload directions.

Chris Coulson: Approve on 2015-03-10

Medium

Fix Released

1008. By Olivier Tilloy on 2015-03-11: Add a DCHECK for the passed in size in BrowserContextIOData,
to make it clear to anyone who writes a new port that they need to limit the size.
1007. By Olivier Tilloy on 2015-03-10: Enforce an upper limit to avoid integer overflow.
1006. By Olivier Tilloy on 2015-03-10: Make the unit for maxCacheSizeHint MB instead of bytes.
The initial cache size is about 1MB when it's created anyway, and given that this is not a hard limit it doesn’t make sense to create an illusion that applications can control the cache size to the nearest byte.
1005. By Olivier Tilloy on 2015-03-06: Do not allow setting the max cache size hint to a negative value.
1004. By Olivier Tilloy on 2015-03-06: Rename maxCacheSize to maxCacheSizeHint to reflect the fact that the limit is a soft one.
1003. By Olivier Tilloy on 2015-03-06: Default to 0 for the max cache size: chromium will pick a size based on available disk space.
1002. By Olivier Tilloy on 2015-03-06: Add WebContext.maxCacheSize property.
1001. By Chris Coulson on 2015-03-04: Bump Chromium rev to 42.0.2311.15
1000. By Olivier Tilloy on 2015-03-04: Add a unit test to verify that restoring the state of a navigation that had triggered an error triggers the error again.
Also update an existing test to verify that reloading a page that had triggered an error generates the same sequence of load events.
999. By Alexandre Abreu on 2015-03-04: Fix sendMessageNoReply crash

This branch contains Public information

Everyone can see this information.