memory usage too high and doesn't reduce |
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. Start up Chrome. 2. Leave Chrome open for a long time (multiple days to weeks) and continue to use it normally. Throughout this time I leave some tabs open the entire time and open and then close some tabs, but the total number of open tabs is relatively constant. I.e., the memory increase over time is NOT because I keep opening and not closing more and more tabs. 3. Notice that Chrome memory usage continues to increase as per More Tools -> Task Manager. 4. Notice that some Chrome Tasks (tabs) take significant amounts of memory. For example, my GMail tab usually exceeds 1,000,000K (1GB). 5. Further notice that closing a tab that uses a lot of memory does not cause Chrome as a whole (the "Browser" task) to reclaim and reduce usage. What is the expected behavior? Chrome should not continue to use more and more memory, and it should reclaim memory when tabs are closed. What went wrong? Chrome just keeps using more and more memory to the point that it needs to start paging and slows down the entire system. For example, at the moment the "Browser" task is using ~8,060,000K (8GB) memory. Did this work before? N/A Chrome version: 55.0.2883.87 Channel: stable OS Version: Flash Version: I found issue https://bugs.chromium.org/p/chromium/issues/detail?id=393395 and saw the comment about running a trace with memory-infra. I tried to do that and after collecting data I received this error: While importing: Error: Couldn't create an importer for the provided eventData. at Import.createImporter_ (chrome://tracing/tracing.js:1348:3342) at Import.createImports (chrome://tracing/tracing.js:1343:21) at Task.run (chrome://tracing/tracing.js:2062:13) at runAnother (chrome://tracing/tracing.js:2074:136) at runTask (chrome://tracing/tracing.js:2037:57) at processIdleWork (chrome://tracing/tracing.js:2043:116) at window.requestIdleCallback.timeout (chrome://tracing/tracing.js:2031:81)
,
Jan 25 2017
Thanks for filling the bug. We have recently fixed a memory usage related bug( crbug.com/678768 ) and the fixed version is now at Beta channel(56.0.2924.60). Could you update your chrome to that version(yeah, it still takes time to roll out to stable) and see whether the memory usage is reduced?
,
Apr 21 2017
Hi rmager@, are you still experiencing this issue? If not, we will archive this bug. Thanks.
,
Apr 21 2017
My issue seems to be fixed. Thanks.
,
Apr 21 2017
Thank you for providing more feedback. Adding requester "zhongyi@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 21 2017
Wontfix this issue since user no longer experienced the issue. It might be related to crbug.com/678768 and 700617 which has been fixed now. |
||||
►
Sign in to add a comment |
||||
Comment 1 by rmager@google.com
, Jan 24 2017