Bug 11683 - Possible memory leak with removing IFRAMEs through JavaScript?
Summary: Possible memory leak with removing IFRAMEs through JavaScript?
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Frames (show other bugs)
Version: 419.x
Hardware: Macintosh OS X 10.4
: P3 Minor
Assignee: Nobody
URL: http://warp.staff.spin.de/iframe-test...
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-23 03:53 PST by Markus Peter
Modified: 2007-02-22 01:40 PST (History)
0 users

See Also:


Attachments
Test case (812 bytes, text/html)
2006-11-23 03:58 PST, Markus Peter
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Peter 2006-11-23 03:53:44 PST
I noticed that on pages which add and remove IFRAMEs through scripting, an empty item will remain in Safari's Activity window for that IFRAME even though it's gone from the DOM and thought I better report it as it might be a small memory leak. I'm not completely sure whether this is just a display issue in Safari or a true WebKit problem.

I added a reduced test case at the above mentioned URL - it will add and remove 20 IFRAMEs after pressing the "Start" button.
Comment 1 Markus Peter 2006-11-23 03:55:53 PST
(oops, I read the priorities explanation too late, sorry for mail spamming)
Comment 2 Markus Peter 2006-11-23 03:58:24 PST
Created attachment 11619 [details]
Test case
Comment 3 Maciej Stachowiak 2007-02-22 01:40:43 PST
I don't think this is a memory leak. The Activity window tracks every resource ever loaded by that page, including ones that are no longer in use. But that goes away once the page is closed.