Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 327440 - Memory leak problem with Iframe in Internet Explorer
Summary: Memory leak problem with Iframe in Internet Explorer
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.3   Edit
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: 1.4 M7   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-11 08:46 EDT by Siarhei Navatski CLA
Modified: 2011-04-04 09:19 EDT (History)
1 user (show)

See Also:


Attachments
Memory leak demo in RAP project (6.05 KB, application/octet-stream)
2010-10-11 08:49 EDT, Siarhei Navatski CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Siarhei Navatski CLA 2010-10-11 08:46:28 EDT
I'm found memory leak problem while using Iframe extended component, for example Browser in Internet Explorer (v. 7 and 8 ).

Use case is the following:
1. create Browser component with URL to some static html page
2. display this component on UI by adding to some composite
3. browser loads html that create some big JS-object
4. dispose this Browser component from UI

As a result memory allocated by loaded html page is not disposed in Internet Exporer. It is disposed normally in FireFox and Chrome browsers.

As I see problem is related to disposing QooxDoo qx.ui.embed.Iframe object. It is not disposed correctly in Internet Explorer.
Comment 1 Siarhei Navatski CLA 2010-10-11 08:49:23 EDT
Created attachment 180597 [details]
Memory leak demo in RAP project
Comment 2 Tim Buschtoens CLA 2010-11-18 14:58:54 EST
Fixed in CVS-HEAD.

In IE, the Iframe must first load an empty page before its removed from dom. Also, the element itself should be destroyed using innerHTML.
Comment 3 Tim Buschtoens CLA 2011-04-04 09:05:25 EDT
The fix does not longer work after fixing Bug 334350.
Comment 4 Tim Buschtoens CLA 2011-04-04 09:19:59 EDT
Updated fix by calling syncSource in destroy function.