NEW 67325
By default, WebKit2 has an enabled but 0-capacity page cache, which results in unnecessary work on many navigations 
https://bugs.webkit.org/show_bug.cgi?id=67325
Summary By default, WebKit2 has an enabled but 0-capacity page cache, which results i...
Adam Roben (:aroben)
Reported 2011-08-31 15:00:23 PDT
WebKit2 defaults to having the page cache enabled. It also defaults to CacheModelDocumentViewer, which specifies that the page cache's capacity should be 0. This means that on most navigations we create a CachedPage and then immediately destroy it. This seems silly, and might also have a negative effect on performance. I haven't looked to see whether WebKit1 has the same issue, but it seems likely.
Attachments
Add attachment proposed patch, testcase, etc.
Note You need to log in before you can comment on or make changes to this bug.