[meta] Chrome browser malloc usage stays up after closing tabs |
||||
Issue descriptionThis 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.
,
May 10 2016
,
Jan 4 2017
,
Nov 7
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 |
||||
Comment 1 by ssid@chromium.org
, Mar 23 2016