Unstoppable memory leak when I open the devtools |
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome on my 2. Open the devtools 3. What is the expected behavior? Nothing much. What went wrong? Chrome's memory usage goes dramatically up (10's of megabytes per second), eventually filling my computer' s memory and entirely freezing it. The only way to stop it is to kill Chrome's main process. Shutting down chrome doesn't stop it. Also, Chrome's task manager can't tell which particular chrome process is using the memory. Did this work before? N/A Chrome version: 65.0.3325.162 Channel: stable OS Version: 4.9.0-6-amd64 Flash Version: I am aware this behavior is very specific to my setup. I couldn't reproduce on a colleague's computer, or on the latest chrome version. I have although: - uninstalled all my extensions. - rebooted my computer. - uninstalled and reinstalled Chrome. The problem is serious enough for me that I would like to investigate deeper. I will gladly provide more detailed information if I am told where to get the relevant ones.
,
Mar 19 2018
,
Mar 19 2018
Unable to reproduce the issue on chrome reported version 65.0.3325.162 using Ubuntu 14.04 with steps mentioned below: 1) Launched chrome reported version and opened Devtools 2) Opened chrome Task manager and observed memory usage, didn't observed any increase in chrome's memory usage. @Reporter: Please provide your chrome GPU details from chrome://gpu which helps us in further triaging it. Thanks!
,
Mar 21 2018
As mentioned in my comment above, after removing my profile, the bug is gone so I can't reproduce for now. It's ok to close this bug, and I will signal it if the bug happens again.
,
Mar 21 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 21 2018
Unfortunately, we don't have enough information to investigate this issue and it is unlikely that such information will become available at a later point. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by galbrun@google.com
, Mar 16 2018