New issue
Advanced search Search tips

Issue 914801 link

Starred by 2 users

Issue metadata

Status: Unconfirmed
Owner: ----
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Tab becomes completely unresponsive and CPU at 100%

Reported by mikehoff...@gmail.com, Dec 13

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Example URL:
facebook.com is one site causing this repeatedly, but I've seen it on a few now

Steps to reproduce the problem:
Random sites, including facebook.com, become unresponsive, or just do not load, and a Google Chrome Helper process is running at 100% CPU

What is the expected behavior?

What went wrong?
CPU usage high by one Chrome process and tab completely unresponsive

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes 

Does this work in other browsers? Yes

Chrome version: 71.0.3578.98  Channel: stable
OS Version: OS X 10.14.2
Flash Version: 

As far as I can tell, this started on 12/12/2018
 
Screen Shot 2018-12-13 at 9.46.51 AM.png
31.8 KB View Download
Components: -Blink
Labels: Stability-Hang Needs-Feedback
Can you please take a sample of the hanging process via Activity.app and attach it here? Thanks.
Labels: Needs-Triage-M71 Needs-Bisect
Having a similar issue, unable to pinpoint root cause, I disabled all extensions to be sure. Using Chrome 72.0.3626.17 64 bit on latest Mac OS. How can I help you debug it?
wouaren@:

1) Go to Activity Monitor
2) Find the misbehaving process
3) Wrench menu
4) "Sample process"
5) Save the result to a file and attach it here
Ok done, I tried to take the sample process when the browser was failing but since this it's freezing at random times, super hard to do it.

Let me know if it would be better to take those when it's actually freezing. Ill try to do that if necessary.
Sample of Google Chrome.txt
212 KB View Download
If you can catch it in the act, that would be best.

Your sample is unfortunately not catching Chrome doing anything other than sitting idle. :(

Sign in to add a comment