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

Issue 649678 link

Starred by 3 users
Status: WontFix
Owner: ----
Closed: Jan 2017
Cc:
█ krajshree@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Closing a popup window/new tab in Chrome doesn't seem to release the memory

Reported by stowe...@gmail.com, Sep 23 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.34 Safari/537.36

Steps to reproduce the problem:
1. First I opened the Chrome task manager, right-clicked and selected "JavaScript memory"
2. Next I navigated to a test page that has a link that opens a new popup window when clicked
3. The popup window loads a page that includes a lot of large third-party JavaScript libraries
4. I checked the Chrome task manager and the JavaScript ram had increased significantly for the test page after opening the popup
5. Finally, I closed the popup window and waited, but the memory usage basically stayed where it was at. Clicking the "Collect garbage" button in the timeline doesn't really free any of the memory. 

What is the expected behavior?
I would expect the browser to release the memory held by the popup window/tab when it is closed

What went wrong?
The memory usage kept increasing each time the popup window was opened, and never really went back down.

Did this work before? N/A 

Chrome version: 54.0.2840.34  Channel: beta
OS Version: 6.3
Flash Version: Shockwave Flash 23.0 r0

I tried this test in IE and Firefox, and when closing the popups in those browsers the memory usage goes down as expected. I'm attaching a zip file with two simple html pages. One page has a button that opens a new tab with the other page. The second page simply creates a large JS array. Closing that tab doesn't free the ram (tabs seem to have the same symptoms as popup windows)
testpages.zip
641 bytes Download

Comment 1 by phistuck@chromium.org, Sep 23 2016

Components: Blink>MemoryAllocator>GarbageCollection
Labels: Performance-Memory

Comment 2 by ligim...@chromium.org, Sep 27 2016

Labels: Needs-Bisect

Comment 3 Deleted

Comment 4 by krajshree@chromium.org, Sep 30 2016 

Unable to reproduce the issue on Windows 10 using chrome stable #53.0.2785.116 and reported version #54.0.2840.34.
Attached a screen cast for your reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened the Chrome task manager, right-clicked and selected "JavaScript memory".
2. Navigated to the downloaded test page that has a link that opens a new popup window when clicked.
3. The popup window loaded a page that includes a lot of large third-party JavaScript libraries.
4. Checked the Chrome task manager and observed that the JavaScript memory did not increase significantly and worked as expected.

stowellt@ - Could you please check this issue on chrome stable #53.0.2785.116 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Comment 5 by ranjitkan@chromium.org, Jan 19 2017

Cc: ranjitkan@chromium.org
Labels: -Needs-Feedback -Needs-Bisect
Status: WontFix (was: Unconfirmed)
Closing the issue as did not hear back from user again. Please feel free to raise a new issue or reopen if the issue still persists or reappears.

Removing Bisect and feedback label.

Thanks.!
►

Sign in to add a comment