Chrome Freezes constantly on many sites since macOS 10.12.4
Reported by
liqu...@gmail.com,
Apr 28 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36 Example URL: https://twitter.com/realDonaldTrump Steps to reproduce the problem: 1. Go to https://twitter.com/realDonaldTrump What is the expected behavior? Browser works without freezing and being unresponsive for 10-20 seconds. What went wrong? Chrome is completely unresponsive, shows a spinning beachball/pinwheel for 10-20 seconds. Often it will come back to life and then repeat the same if I scroll a bit. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? Yes 57 Does this work in other browsers? Yes Chrome version: 58.0.3029.81 Channel: stable OS Version: OS X 10.12.4 Flash Version: Ever since I upgraded to macOS 10.12.4, visiting many resource-intensive sites causes all of Chrome to freeze, be completely unresponsive, and show a spinning beachball/pinwheel for 10-20 seconds. Often it will come back to life and then repeat the same if I scroll a bit. An (unfortunate) example with which I am always able to reproduce this error is https://twitter.com/realDonaldTrump, but there are many others. Safari doesn't have this problem. What I have already tried: - New, clean user profile. - Uncheck hardware acceleration. - Open Keychain Access/Preferences and Disable CRL. - Canary, Beta, Stable Chromes. - Incognito, Guest. - Completely delete all local data including extensions, Profiles and Chrome and reinstall. - Create a new user account on my Mac. Nothing remotely fixes the problem. The only thing I have discovered to slap a bandaid on the problem is to use the uBlock Origin extension and manually block many things on an offending site, such as auto-playing HTML5 videos. But, I have to do this manually for every site I visit. So instead, I have just switched to Safari except for web sites I am working on (I am a web developer). I also believe I have isolated this problem to macOS 10.12.4, because I have another Mac on 10.12.3 which did not have this problem. As soon as I updated to 10.12.4, it did. It is possible that there was a Chrome update at the same time though, I suppose.
,
Apr 28 2017
Please do the following: 1. Launch Chrome 2. Launch Activity Monitor 3. Select Chrome in Activity Monitor's list of apps 4. Go back to Chrome and get it to freeze 5. Go back to Activity Monitor and choose View -> Sample Process and then save the sample output as a file and attach it to this bug report.
,
Apr 29 2017
Here you go. I created a new user profile just before creating this sample. Let me also add that the freezing is not isolated to the offending tab, it freezes the entire Chrome app, all tabs, profiles, windows including the chrome task manager are unresponsive.
,
Apr 29 2017
Thank you for providing more feedback. Adding requester "shrike@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 1 2017
,
May 1 2017
Okay, I think I have solved this issue, thanks to the symbolized sample pointing out the problem was with TextToSpeech. The issue was that I had followed advice to manually delete all voices in order to save hard drive space (http://osxdaily.com/2011/07/29/delete-voices-mac-os-x-lion/). In order to add one back I had to go to System Preferences/Accessibility/Speech, check Enable Announcements, and go into Options to add a voice. Seems to have solved the issue.
,
May 1 2017
Looks like macOS freezes if you have no voices installed. This isn't a bug in Chrome, it's in Apple's own code.
,
May 1 2017
dmazzoni@ - would you please file a rdar on this?
,
May 2 2017
Also let me clarify that 10.12.4 WAS the breaking change - I had deleted the voices multiple OS versions ago and Chrome only started having trouble with 10.12.4.
,
Nov 16 2017
Fixed on Apple's end |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by rbyers@chromium.org
, Apr 28 2017