[Webkit-unassigned] [Bug 64483] Disable Caches in Safari's Develop menu does not disable caches.

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Mar 15 22:36:49 PDT 2016


https://bugs.webkit.org/show_bug.cgi?id=64483

Darin Adler <darin at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |darin at apple.com

--- Comment #2 from Darin Adler <darin at apple.com> ---
OK, here are the two bugs I found:

1) Setting the cache model to CacheModelDocumentViewer does not turn off MemoryCache. It turns off caching of dead resources, but it sets a non-zero value for the total size of the memory cache, which means that live resources are indeed cached. This policy is implemented in the calculateCacheSizes function and the +[WebView _setCacheModel:]  method. I tried setting cacheTotalCapacity to 0 and indeed this fixed the original reported symptom. It might be bad, however, for clients using CacheModelDocumentViewer for something other than Safari’s Disable Caches. Performance might be suprisingly bad when the memory cache is entirely turned off. Presumably this regression dates back to when we Antti created the MemoryCache.

2) Setting the cache model to CacheModelDocumentViewer does not turn off the NSURLCache disk cache when NETWORK_CACHE is disabled. This policy is in the NetworkProcess::platformSetCacheModel function and the +[WebView _setCacheModel:]  method. Neither will ever shrink disk capacity, only make it larger. Comment says, “Don't shrink a big disk cache, since that would cause churn.” I don’t understand the thinking behind this. This has always been the case <http://trac.webkit.org/changeset/25430>. Safari attempts to work around this by calling -[NSURLCache setDiskCapacity:] directly but this has not had any effect on WebKit networking since we moved it from the UI process to the web process and then later to the network process.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160316/d8a3fdd7/attachment.html>


More information about the webkit-unassigned mailing list