Bug 17469 - Memory leak in CachedImage
Summary: Memory leak in CachedImage
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: 528+ (Nightly build)
Hardware: Other Linux
: P2 Major
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-21 01:10 PST by Saugata Das
Modified: 2017-03-11 11:02 PST (History)
6 users (show)

See Also:


Attachments
Provides logs for the memory leak (11.81 KB, text/plain)
2008-02-21 01:12 PST, Saugata Das
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Saugata Das 2008-02-21 01:10:14 PST
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.
Comment 1 Saugata Das 2008-02-21 01:12:53 PST
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.
Comment 2 Alexander Butenko 2009-03-17 13:07:50 PDT
long time passed since bug was submitted. Probably was already fixed? If not i think it worth to take a look on it.
Comment 3 GaoXiong 2011-07-22 00:06:51 PDT
This bug is still there!
Comment 4 Alexey Proskuryakov 2011-07-22 14:43:25 PDT
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.
Comment 5 GaoXiong 2011-07-23 00:29:43 PDT
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.
Comment 6 Elliott Sprehn 2012-07-30 15:42:36 PDT
Seems like this would likely be resolved by landing 82287
Comment 7 Alexander Butenko 2012-07-30 18:52:39 PDT
(In reply to comment #6)
> Seems like this would likely be resolved by landing 82287

Wow, guys, 4 long years...