GPU Process pegs core, uses 1.7GB+ RAM - multiple computers, inconsistent
Reported by
explan...@gmail.com,
Jul 6 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: Issue across multiple Win7SP1x64 computer models in our company where Chrome's "GPU Process" grows to consume 1.7GB+ of RAM, and while it's growing, pegs a CPU core to 100%. This started occurring on random computers in version 58 or earlier, but I'm only now reporting it because I assumed it was a known issue. Computer models include multiple Dell desktops and laptops across multiple hardware generations running Intel display drivers. We also use Webroot SecureAnywhere with uBlock Origin, but most computers have no issues. Making this problematic is that it's often not consistent. Sometimes rebooting will fix it. Sometimes removing all management registry keys and starting Chrome fixes it. Other times the user just has to get back to work and switches to using Firefox. I can't reproduce this in a testing environment except rarely. Chrome doesn't crash. It just sits there using a ton of RAM and CPU time. I've provided about:GPU and a screenshot of the issue. Unfortunately, I can now no longer reproduce the issue on this machine. What is the expected behavior? Normal resource usage What went wrong? Inflating GPU Process RAM usage and CPU usage by chrome.exe Did this work before? Yes Started at minimum version 58 Chrome version: 59.0.3071.115 Channel: stable OS Version: 7 SP1 x64 Flash Version: I'm looking for advice on what debugging information I can gather to better help diagnose this issue. I realize I haven't provided you much to go on.
,
Jul 6 2017
,
Jul 6 2017
Additional info: Updating the Intel GPU drivers with Dell-approved versions does not appear to help.
,
Jul 6 2017
Does the bug happen if you disable "Use hardware acceleration when available" in browser settings?
,
Jul 6 2017
Or you can disable just GPU rasterization on chrome://flags page as it's known to be finicky: chrome://flags/#enable-gpu-rasterization
,
Jul 7 2017
,
Jul 9
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
,
Jul 20
Archiving this bug since there hasn't been a lot of activities going on. If the issue persists, please file a new bug. Thank you. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by explan...@gmail.com
, Jul 6 2017