Bug 17469 – Memory leak in CachedImage

• Status: UNCONFIRMED
• Component: WebKitGTK

[Saugata Das]

Scenario:
1. Start browser
2. Browse to www.yahoo.com. After it loads the page, browse www.rediff.com.

We are working on a gtk port for WebKit. We are using release r30123. As we are working on a handheld device resource utilization is a major factor.
We can see a huge number of undeleted CachedImages. FrameView, HTMLImagesLoader are not getting deleted which results in CachedImage not being deleted. This is resulting in quite a big amount of memory leak.

[Saugata Das]

Created attachment 19253 [details]
Provides logs for the memory leak

The text file gives a log for counts of FrameView,HTMLImageLoader, and CachedImage construction and destruction.

[Alexander Butenko]

long time passed since bug was submitted. Probably was already fixed? If not i think it worth to take a look on it.

[GaoXiong]

This bug is still there!

[Alexey Proskuryakov]

What is the bug here? Is it Gtk-only as suggested by component?

CachedImage objects certainly aren't destroyed when a frame is destroyed, precisely because they are cached.

[GaoXiong]

It's not only on GTK but also on other platforms like windows (my IDE is vs2005).

CachedImage objects won't be destroyed even when the document is destroyed.

The test case is very simple:
1. Load a page with one picture
2. Close the browser
The we can see "LEAK: 1 CachedResource" in the output window.

[Elliott Sprehn]

Seems like this would likely be resolved by landing 82287

[Alexander Butenko]

(In reply to comment #6)
> Seems like this would likely be resolved by landing 82287

Wow, guys, 4 long years...