Chrome beachballs intermittently on macOS, becoming totally unresponsive
Reported by
alex.gay...@gmail.com,
Apr 1 2018
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: Unknown! It's intermittent, I've seen it 3-4 times in the last month, but I couldn't tell you what causes it. What is the expected behavior? What went wrong? It beachballed :-) Did this work before? N/A Chrome version: 65.0.3325.181 Channel: stable OS Version: OS X 10.13.4 Flash Version: I have attached a sample taken with Activity Monitor. The only thing of note about my browser is that I run with full Site Isolation enabled. I've waited at least 60 seconds after it begins beachballing, and it does not recover in that time frame, forcing me to force quit Chrome.
,
Apr 3 2018
Unable to reproduce this issue on 65.0.3325.181 using Mac 10.13.3 when site isolation is enabled. Used the build for almost half a day and didn't observe any unresponsiveness. @Reporter: Are you seeing any crash id in chrome://crashes As per comment#0 adding Internals>Sandbox>SiteIsolation component. Could someone from dev team please have a look at .txt file given.
,
Apr 3 2018
@reported, do you have --site-per-process or "Strict Site Isolation" enabled? It isn't on stable by default yet, so it will be useful to know which direction to look into. Assigning to wjmaclean@ as per comment 3, as it looks input event related.
,
Apr 3 2018
This seems like a duplicate of issue 818214 (based on #c3 which mentions content::GestureEventQueue::ProcessGestureAck). Sorry for piling even more questions, but... reporter@: was DevTools possibly used during the repro to turn on emulation of a mobile device in Chrome? Did you try to use mouse to simulate touch events shortly before the hang happened? (answers might help us confirm is the root cause is issue 824772 )
,
Apr 3 2018
alex.gaynor@ - Would you be able to retry with a recent build (Canary channel even?). If lukasza@ is right, then it may be fixed in a more recent build.
,
Apr 3 2018
Bunch of questions, let me try to answer them all: 1) Nothing in chrome://crashes 2) Site Isolation was enabled with the "Strict site isolation" option in chrome://flags 3) DevTools was almost definitely used in the browsing session when this happened, but not emulation of mobile devices. 4) This is intermittent and non-reproducible, so I can't attempt reliably test Canary for this.
,
Apr 3 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 6 2018
alex.gaynor@ Thanks for the update. Unable to reproduce the issue on Mac OS 10.13.3 on the reported version 65.0.3325.181 and the latest Canary 67.0.3389.0. As per comment #7, as the issue is intermittent and not reproducible at reporter's end, adding 'TE-NeedsTriageHelp' label and requesting Internals>Sandbox>SiteIsolation team to look into this issue and help in further triaging. Thanks..
,
Apr 16 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by vamshi.kommuri@chromium.org
, Apr 1 2018