[Webkit-unassigned] [Bug 108960] [GTK] Remove subresource leaks from WebKit1 and WebKit2

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Feb 11 08:51:11 PST 2013


--- Comment #14 from Martin Robinson <mrobinson at webkit.org>  2013-02-11 08:53:24 PST ---
(In reply to comment #12)

> If the document loader is caching the subresources, the problem is still there, no?

I haven't confirmed this, but I suspect that the DocumentLoader has an idea of when a subresource is no longer used. In WebKit we are just saving all of them without any eviction policy.

> I'm not sure I understand this, we would create different WebKitWebResource objects, one to wrap the resource while loading to pass it to the signals and a different one to return in get_subresources. The former would be owned by webkit and released when the resource load finishes while the latter would be owned by the caller and not cached by webkit.

That's pretty close, but it seems like that would cause the subresources to continue to leak. Applications still aren't expecting to receive a transfer=full reference. What we could do is to deref any resources we create in a timeout though.

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