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

Issue 593485 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 7
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocked on:
issue 593486
issue 593500
issue 610551



Sign in to add a comment

[meta] Chrome browser malloc usage stays up after closing tabs

Project Member Reported by ssid@chromium.org, Mar 9 2016

Issue description

This is a meta-bug to track memory reduction efforts.

Steps:
1. Open multiple tabs, perform actions.
2. Close all the tabs, wait for 10-60 seconds and measure memory.
3. Chrome memory stays up.

This is a common problem for everyone using chrome.

Results of heap profiling can be seen in these docs:

https://docs.google.com/document/d/1f88Z1QsynOvDnkV_hP3ez1vwEvhjgIhC6Je8H5zL5uc/edit#heading=h.ty8ognouxs8x

https://docs.google.com/a/google.com/document/d/1dLHOzmzhH4nUtb3_3P2k5ZPTCmJ3nC6syYHxTuZFMUQ/edit?usp=sharing

Now lets try to reduce some memory.
 

Comment 1 by ssid@chromium.org, Mar 23 2016

Labels: -Performance-Memory Performance-Memory-Browser

Comment 2 by ssid@chromium.org, May 10 2016

Blockedon: 610551
Components: Internals>Instrumentation>Memory
Status: WontFix (was: Untriaged)
This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.

Sign in to add a comment