[Webkit-unassigned] [Bug 49008] Unbounded memory growth for long lived pages with many requests
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Jan 17 23:09:21 PST 2011
https://bugs.webkit.org/show_bug.cgi?id=49008
--- Comment #26 from Pavel Feldman <pfeldman at chromium.org> 2011-01-17 23:09:20 PST ---
Let me dump Web Inspector assumptions here:
- When inspector is opened, it traverses Frame tree and collects frame resources using CachedResourceLoaders (cachedResourceLoader()->allCachedResources() calls).
- Once opened, it updates this tree of resources to keep it up-to-date based on the network events.
- At any time user wants to see the resource content, we either use frameLoader->documentLoader()->mainResourceData() (for main resource) or use its CachedResourceLoader again.
It is important for us to show the entire tree of resources to the user. Aggressive clearing of the cachedresourceloader will probably regress our functionality. Worst case we should mark CachedResources as "emptied" in order to re-create the resource tree structure properly. Unfortunately there are no tests that would regress, but if we make the wipe threshold configurable, it would not be hard to come up with one.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list