Bug 17469

Summary: Memory leak in CachedImage
Product: WebKit Reporter: Saugata Das <saugatad>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: UNCONFIRMED    
Severity: Major CC: a.butenka, ap, bugs-noreply, esprehn, porgao, saugatad
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: Linux   
Attachments:
Description Flags
Provides logs for the memory leak none

Saugata Das
Reported 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.
Attachments
Provides logs for the memory leak (11.81 KB, text/plain)
2008-02-21 01:12 PST, Saugata Das 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Saugata Das
Comment 1 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.
Alexander Butenko
Comment 2 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.
GaoXiong
Comment 3 2011-07-22 00:06:51 PDT
This bug is still there!
Alexey Proskuryakov
Comment 4 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.
GaoXiong
Comment 5 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.
Elliott Sprehn
Comment 6 2012-07-30 15:42:36 PDT
Seems like this would likely be resolved by landing 82287
Alexander Butenko
Comment 7 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...
Note You need to log in before you can comment on or make changes to this bug.