Issue metadata
Sign in to add a comment
|
Chromes expanding memory usage when dev tools open
Reported by
danmonro...@gmail.com,
May 1 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome, note memory usage in Activity Monitor is stable for Chrome 2. Open Dev Tools, note memory usage steadily increases 3. Chrome requires Force Quit to quit. What is the expected behavior? Memory remains stable with dev tools open What went wrong? Memory usage for Chrome with dev tools open steadily increases. Will eventually crash. Chrome requires Force Quit to quit. Did this work before? Yes Chrome version: 66.0.3359.139 Channel: stable OS Version: OS X 10.11.6 Flash Version: I've disabled all extensions, signed out, and cleared cookies/storage/etc and it still happens.
,
May 2 2018
Unable to reproduce the issue reported version on 66.0.3359.139 by using Mac 10.12.6. Attaching Screencast for reference. Steps -------- 1.Launched Chrome and Activity Monitor 2. Observed the memory usage in Activity Monitor is stable for Chrome 3. Opened Dev Tools, Observed memory usage steadily increases and decreases 4. Observed chrome working fine and not required to Force Quit. 5. Observed there is no crashes in the chrome. As we are unable to reproduce the issue from our end. Can you verify this issue with fresh profile that is not having any extensions and apps.Let us know still issue is persists. Thanks!
,
May 2 2018
Yes, I can confirm that a new profile does not have the new issue. Now I have to figure out what in my profile is causing the memory issue. Thanks
,
May 2 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
,
May 3 2018
As per C#0 this eventually results in crash.Could you please attach any crash id from chrome://crashes to debug this further.
,
May 3 2018
Uploaded Crash Report ID cb3d6c6129b2406c (Local Crash ID: 19816485-9e87-4e27-aa39-09414dff3756) Crash report captured on Thursday, May 3, 2018 at 12:23:31 PM, uploaded on Thursday, May 3, 2018 at 12:23:31 PM
,
May 3 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
,
May 4 2018
Thank you for providing information... As per comment #7 we forwarding this issue to Inhouse Team to check the crash id and help in triaging accordingly. Thanks..!
,
May 4 2018
Uploaded Crash Report ID 90febe2cf4afca40 (Local Crash ID: ea403f6e-e6b3-4a3b-a3e9-9db2f950b8cf)
,
May 7 2018
Magic signature and Stack trace of the above Crash I'd looks similar to issue 797817. Hence merging into it, Please feel free to un dupe if not the case. Removing Needs-Bisect label as this is not reproducible from our end. Thanks!!
,
May 7 2018
I don't have permission to view issue 797817 so I can't tell you if is a dup or not.
,
May 7 2018
Uploaded Crash Report ID b3cdca2d07286bbd (Local Crash ID: 98dc6648-f936-4527-aaf0-df24e2f29ce1) Crash report captured on Monday, May 7, 2018 at 2:51:39 PM, uploaded on Monday, May 7, 2018 at 2:51:40 PM |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, May 1 2018