Bug 141911 - Hang while Feedly is idling
Summary: Hang while Feedly is idling
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: Page Loading (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Myles C. Maxfield
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-23 09:27 PST by Myles C. Maxfield
Modified: 2015-08-26 23:41 PDT (History)
3 users (show)

See Also:

Attachments
Sample (68.40 KB, text/plain)
2015-02-23 09:27 PST, Myles C. Maxfield 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Myles C. Maxfield 2015-02-23 09:27:14 PST 
Created attachment 247124 [details]
Sample

See attached sample.
Comment 1 Alexey Proskuryakov 2015-02-23 22:43:24 PST 
> 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.
Comment 2 Antti Koivisto 2015-02-24 08:21:47 PST 
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?
Comment 3 Alexey Proskuryakov 2015-02-24 11:07:14 PST 
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));
Comment 4 Myles C. Maxfield 2015-08-26 23:41:28 PDT 
Has not reproduced.