Growing memory from opening images in DOM and removing them
Reported by
benjamin...@gmail.com,
Jul 1 2016
|
|||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36
Steps to reproduce the problem:
It seems that Chrome holds on to displayed images in memory even after the image has been removed from the DOM. Following pseudo code demonstrates the problem
for (let i = 0; i < 10000; ++i) {
let e = document.createElement('img')
e.src = 'file:///tmp/1.bmp'
document.body.appendChild(e)
setTimeout(() => { document.body.removeChild(e) }, 1000)
}
What is the expected behavior?
Once an image is taken out of the DOM, its resources are freed.
What went wrong?
Memory grows until you get an out of memory crash.
Did this work before? N/A
Chrome version: 4.9.385.28 Channel: stable
OS Version: OS X 10.11.5
Flash Version: Shockwave Flash 22.0 r0
,
Jul 5 2016
benjamin.pasero@ Thnaks for the issue. Could you please provide us any sample test file or URL to triage the issue from test team end. Thanks,
,
Aug 4 2016
Closing this issue due to lack of user feedback. Please feel free to raise a new issue if the issue still persists for you on latest stable. Thanks, |
|||
►
Sign in to add a comment |
|||
Comment 1 by ccameron@chromium.org
, Jul 1 2016