Summary: | Hang while Feedly is idling | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Myles C. Maxfield <mmaxfield> | ||||
Component: | Page Loading | Assignee: | Myles C. Maxfield <mmaxfield> | ||||
Status: | RESOLVED WORKSFORME | ||||||
Severity: | Normal | CC: | ap, cdumez, koivisto | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
> WKCFURLCacheCopyAllHostNamesInPersistentStoreForPartition
This is a nightly or local build, isn't it supposed to use WebKit persistent cache, and not CFNetwork's?
I don't know if this could happen when actually idling, something needed to send that clearCacheForOrigin message first.
Why is this cache clearing code running in a web process in the first place? For the legacy networking that doesn't use network process? Probably, not sure. // FIXME (Multi-WebProcess): <rdar://problem/12239765> There is no need to relaunch all processes. One process to take care of persistent cache is enough. processPool()->sendToAllProcessesRelaunchingThemIfNecessary(Messages::WebResourceCacheManager::ClearCacheForOrigin(securityOrigin, cachesToClear)); Has not reproduced. |
Created attachment 247124 [details] Sample See attached sample.