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

Thu Dec 16 16:57:36 PST 2010

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

Kevin Gadd <kevin.gadd+bugzilla at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kevin.gadd+bugzilla at gmail.c
                   |                            |om

--- Comment #8 from Kevin Gadd <kevin.gadd+bugzilla at gmail.com>  2010-12-16 16:57:36 PST ---
(In reply to comment #5)
> (From update of attachment 60885 [details])
> I didn't look at the patch, but I assume that it implements what the above comment describes.
> 
> The reason for m_documentResources existence is so that we could provide a list of resources to clients via -[WebDataSource subresources], store them in Web archives, and show them in Web Inspector. Thus, removing items just because the resource data is no longer cached is inappropriate.

I have recently discovered that this bug makes an application I'm building unusable on any modern WebKit-based browser, as it exhausts available memory within minutes. I've yet to find a workaround, so I decided to come see if perhaps I could at least submit a patch that fixes the bug and hope that it makes its way to devices like the iPhone in a reasonable amount of time.

Am I interpreting your statement correctly that you believe that this memory leak is intended behavior and should be preserved simply to keep Web Inspector's current behavior? I understand the desire to have web inspector offer a list of all resources ever loaded by a page, but doing it in this way breaks a large set of web development use cases. This seems an extreme cost to pay merely to get a feature of questionable value within Web Inspector. At the very least, this unbounded memory consumption should only be triggered when resource tracking has been explicitly requested by the user.

Is there a way that this bug can be fixed and still meet your functionality requirements for Web Inspector? If you can describe the requirements for an acceptable fix, I can attempt to create that fix.

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