Browser process gets stuck endlessly using >100% CPU (spinning on one core) |
|||||||
Issue descriptionChrome Version: 52.0.2743.32 (Official Build) beta (64-bit) Chrome OS Version: 8350.21.1 (Official Build) beta-channel samus Chrome OS Platform: Pixel2 Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1) Shutdown (2) Restart previous browser state (loading multiple tabs) (3) Browser process ends up with at least one thread endlessly spinning. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) With M52, always. 4 reboots and counting, all end up with the parent browser process spinning and consuming a full core endlessly. What is the impact to the user, and is there a workaround? If so, what is it? Entire system is sluggish, battery life is reduced. Please provide any additional information below. Attach a screen shot or log if possible. (Happy to generate and attach a log, but unable to find instructions on how to generate one)
,
Jun 17 2016
,
Jul 4 2016
This issue has been moved once and is lower than Pri-1. Removing the milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 16 2016
What is the URL for the problem web site ? Do you see this in incognito mode ?
,
Jul 18 2016
This issue is not driven by a specific website, the process that is spinning is the core 'browser', not any of the pages. Killing/ending other page tasks does nothing to immediately reduce/remove CPU load in the Browser task. Once triggered, the issue persists in incognito mode.
,
Sep 2 2016
can you file a feedback report ? what about chrome://crashes, does it contain any crash ?
,
Feb 17 2017
,
Mar 18 2017
Activating. Please assign to the right owner and the appropriate priority.
,
Apr 12 2018
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 sheriffbot@chromium.org
, Jun 17 2016