Issue metadata
Sign in to add a comment
|
High CPU usage attributed to "browser"
Reported by
dan...@d15.biz,
Sep 26 2016
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393 Steps to reproduce the problem: Chrome is using a lot of CPU power, and its Task Manager attributes this to "Browser". Is there a way I can debug why this is happening? What is the expected behavior? Chrome does not turn my laptop into a heater What went wrong? Laptop is burning my lap Did this work before? Yes This only broke within the last few weeks - Maybe with Chrome 53 stable or 54 beta Chrome version: 54.0.2840.34 Channel: beta OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0
,
Sep 26 2016
Seems like this was at least partially caused by the "JumpListIcons" directory containing exactly 65535 files. I looked at the Chrome process with Sysinternals Process Monitor and found it continuously reading from/writing to that directory. I just deleted the entire directory and the CPU usage dropped. Now it's still using 7% while idle, but much lower than before.
,
Sep 27 2016
,
Sep 27 2016
,
Sep 28 2016
Need help in reproducing this issue as i don't have "JumpListIcons" directory containing 65535 files. kulshin@ - Could you please provide more inputs on this issue for further investigation. Thanks,
,
Oct 19 2016
I guess some of the fixes here might help: https://bugs.chromium.org/p/chromium/issues/detail?id=40407#c82
,
Oct 21 2016
@kulshin - Gentle ping. Could you please look into this issue. Adding label TE-NeedsTriageHelp
,
Oct 28 2016
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 3 2016
,
Jan 2 2017
Deprecating UI>OSIntegration in favor of the more generic Internals>PlatformIntegration
,
Feb 21 2017
The very act of having Chrome's Task Manager open causes the browser process's CPU usage to rise since the browser process must use CPU to measure the system and update the Task Manager UI. You could try using a program like Process Explorer or Process Hacker to look at the CPU usage of the browser process without Chrome's Task Manager open (the browser proc is the chrome.exe process that is the parent to all others). Let us know if this still seems high given what you see on your machine. Regarding the JumpList icons, fixes have been landing in that corner of the code recently, so other users affected by that particular issue should be rescued soon.
,
Mar 7 2017
,
Mar 29 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dan...@d15.biz
, Sep 26 2016