Chrome spikes CPU and process load randomly freezing machine
Reported by
swart...@gmail.com,
Aug 10 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36 Steps to reproduce the problem: 1. Install google-chrome on debian 9 on thinkpad x1 v3 2. browse the web with multiple tabs open and possibly go to a page with autoplaying video (twitter) 3. Watch as process load gets as high as 40(!) and computer refuses to respond to input for minutes What is the expected behavior? Chrome should have reasonable process load per tab What went wrong? Chrome way overused cpu or processes and completely hung computer Did this work before? N/A Chrome version: 59.0.3071.115 Channel: stable OS Version: Debian 9.0 Flash Version: This happens pretty frequently, multiple times a day. Unfortunately it happens unpredictably, so I have no way to diagnose the root cause. Even with the chrome process manager open (shift+esc) the freezing of my computer prevents me from seeing what resources the effected tab is taking up (i.e. cpu v gpu) because once the computer unhangs it updates it's usage numbers showing it taking a normal amount of cpu/gpu. It would be nice if there was a way to see historic resource usage. Based on when this happens it typically involves the loading of video and large numbers of images. Additionally it seems slightly more common when I am using an external monitor in addition to the one on my laptop. This leads me to guess that it might be related to Chrome's gpu usage and interaction with graphics drivers, but I have no way to confirm. I'm happy to take some steps to help identify the root cause if you can give me suggestions.
,
Aug 10 2017
swartzcr@, thank you for the report. Can you please attach a chrome://trace here? How to get trace: https://www.chromium.org/developers/how-tos/submitting-a-performance-bug
,
Aug 11 2017
62 is a canary build. Have you tried installing stable channel to see if you experience the same issues? Also, please attach a chrome trace as recommended in comment #2.
,
Aug 14 2017
here's a trace of a small flare-up. In general it might be hard to do this since the process locking will cause me to be unable to stop the trace before it fills up the buffer.
,
Aug 14 2017
Thank you for providing more feedback. Adding requester "manoranjanr@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
,
Aug 15 2017
,
Aug 15
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by charliep...@gmail.com
, Aug 10 2017