Issue 64748 in chromium: Memory leak when changing src of IFRAME
chro...@googlecode.com
Owner: ----
Labels: Type-Bug Pri-2 Area-Undefined
New issue 64748 by pastu...@gmx.net: Memory leak when changing src of IFRAME
http://code.google.com/p/chromium/issues/detail?id=64748
Chrome Version :
Chromium 7.0.517.41 (Developer Build 0)
WebKit 534.7
V8 2.3.11.17
User Agent Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.7
(KHTML, like Gecko) Sabayon Chrome/7.0.517.41 Safari/534.7
Command Line /usr/lib/chromium-browser/chrome
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: FAIL
Firefox 3.x: OK
IE 7/8: not tested
What steps will reproduce the problem?
1. Append IFRAME using javascript
2. Repeatedly change the src attribute of the iframe
What is the expected result?
No memory leaks.
What happens instead?
Memory leaks; see screenshots.
On memory constrained machines it introduces heavy swapping. In all cases
the tab will crash after some time (depending on contents and reload count).
Firefox seems to have an upper limit of 256M per Tab, if it the limit
reached old caches are free'd (see attachment: s3.png).
Attachments:
MemoryTest.js 477 bytes
s1.png 55.2 KB
s2.png 56.1 KB
s3.png 21.7 KB
chro...@googlecode.com
Comment #1 on issue 64748 by pastu...@gmx.net: Memory leak when changing
--- Continued ---
Outstanding: More testing on Safari, maybe it has an upper cap like
Firefox, too.
Attachments:
MemoryTest.js : Sample script
s1.png: Memory usage graphs for chrome and safari on windows
s2.png: Like s1, but some time later.
s3.png: Memory usage graphs for firefox on windows
Windows versions:
Google Chrome 7.0.517.44 (Official Build 64615)
WebKit 534.7
V8 2.3.11.22
User Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US)
AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
Command Line "C:\Documents and Settings\Paz\Local Settings\Application
Data\Google\Chrome\Application\chrome.exe"
Safari 5.0.3 (7533.19.4) / Windows XP
chro...@googlecode.com
Comment #2 on issue 64748 by dmz.oneill: Memory leak when changing src of
IFRAME
http://code.google.com/p/chromium/issues/detail?id=64748
nice
chro...@googlecode.com
Comment #8 on issue 64748 by musicisair: Memory leak when changing src of
IFRAME
http://code.google.com/p/chromium/issues/detail?id=64748
This problem isn't just in changing the src of an iframe. If you remove the
iframe from the DOM and then append a new iframe the memory still leaks.
This is NOT a single-page leak as the memory use does not return to normal
after navigating to a new page (within the same tab).
Tested on Windows XP SP3 running Chrome 11.0.672.2 dev with 2.5GB ram.
chro...@googlecode.com
Comment #20 on issue 64748 by lakh...@gmail.com: Memory leak when changing
I havw this problem in Chrome 16.0.912.63 m
chro...@googlecode.com
Comment #21 on issue 64748 by skyma...@gmail.com: Memory leak when changing
Same error in Chrome 18.0.1025.162
chro...@googlecode.com
Comment #22 on issue 64748 by aaronfr...@gmail.com: Memory leak when
Any work-arounds for this? I have an extension that could be awesome, but
is dying like a champ because of this.