New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 623597 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Jul 2016
Cc:
█ kavvaru@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Memory leak when appending image to dom, and removing it

Reported by afayo...@gmail.com, Jun 27 2016 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/50.0.2661.102 Chrome/50.0.2661.102 Safari/537.36

Steps to reproduce the problem:
1. Create an image and appending it to dom
2. Removing it
3. Take a heap snapshot, search for detached dom tree

What is the expected behavior?
We should find no detached dom tree, no detached HTMLImageElement

What went wrong?
The attached example code append a new image to dom (create function).
After calling remove function, there is still an HTMLImageElement in memory.

Did this work before? N/A 

Chrome version: 50.0.2661.102  Channel: n/a
OS Version: Ubuntu 14.04
Flash Version: 

Chrome Windows, no memory leak.
If I append image with onload callback, no memory leak.
I have the same memory leak with video!
memory.png
99 KB View Download
index.html
681 bytes View Download

Comment 1 by kavvaru@chromium.org, Jun 29 2016

Cc: kavvaru@chromium.org
Components: Platform>DevTools
Labels: Needs-Feedback
Unable to reproduce the issue on windows 7, Linux Ubuntu 14.04 using chrome version 51.0.2704.106 with the below steps

1. Opened the attached html on chrome
2.opened dev tools and take heap snapshot
3.In results am not able to find the "detached HTMLImageElement" as like your screen shot but observed only "HTMLImageElement"

Please find the attached screen shot and confirm anything missed here.
Request you once please try the issue by upgrading chrome to latest stable and if the issue still persists please update the thread.

Thanks,
623597.png
68.9 KB View Download

Comment 2 by afayo...@gmail.com, Jun 29 2016 

Ok, I upgraded from Chromium/50.0.2661.102 to chrome/51.0.2704.106

and there is no memory leak ! It seems it was a bug in previous version.

Thank you for your time.
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 29 2016

Labels: -Needs-Feedback Needs-Review
Owner: kavvaru@chromium.org
Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 4 by paulir...@chromium.org, Jul 1 2016

Status: WontFix (was: Unconfirmed)
closing as it appeares fixed in m51

Comment 5 by kavvaru@chromium.org, Jul 21 2016

Owner: ----
►

Sign in to add a comment