[Webkit-unassigned] [Bug 31253] Unbounded memory growth when adding and removing images

[bugzilla-daemon at webkit.org]

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


Alexey Proskuryakov <ap at webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |koivisto at iki.fi




--- Comment #9 from Alexey Proskuryakov <ap at webkit.org>  2010-12-16 17:37:00 PST ---
Note that Web Inspector was not the only client that I mentioned as needing access to document resources. Anyway, I don't think that anyone will argue that secondary functionality (like Activity window or web archives) should prevent web content from working.

It may be just fine to remove resources from m_documentResources when all elements using them are known to have been removed from the document, and won't come back from a detached tree. It's not very easy though, as external resources can also be referenced by style rules, so counting only elements isn't sufficient.

There is some surprising code in CachedResourceLoader today. The attached patch implies that CachedResourceLoader holds a strong reference to document resources - but why does this class have a removeCachedResource() method called from CachedResource destructor then?

It's not obvious that all bugs with memory growth when adding and removing images are the same internally. There may be loader problems, but there may also be JavaScript garbage collection problems. Unless you're 100% sure that you are seeing an identical issue, it may be best to file a separate bug - even if it's found to be a duplicate later, that's much better than discussing two issues in one bug.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.