Installing any extension from Chrome Web store crashes Mac
Reported by
tresheff...@gmail.com,
Mar 29 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.87 Safari/537.36 Steps to reproduce the problem: 1. Open Chrome 2. Menu > More Tools > Extensions 3. Click Get more extensions link 4. Choose an extension from web store (I tried One Tab and any.do) 5. Click Add to Chrome button 6. Button changes to Checking... 7. Mac crashes to login screen 8. After logging in, extension is not installed 9. Repeating above yields same result consistently 10. Disable all existing extensions 11. Repeat above 12. Yields same results What is the expected behavior? The selected extension would be installed What went wrong? Mac crashed. No crashes report in chrome://crashes WebStore page: https://chrome.google.com/webstore/detail/anydo/ocgddccilgpeepgglnlpchkpgamkgmld?hl=en-US Did this work before? Yes When I installed the Last Pass extension about 6 months ago. Chrome version: 49.0.2623.87 Channel: stable OS Version: OS X 10.11.3 Flash Version: Shockwave Flash 21.0 r0 I was working on my own extension locally about 3-4 months ago but abandoned it. It was installed via developer mode but I've since deleted it. Unsure it has an effect but thought worth mentioning.
,
Jun 3 2016
I can't reproduce this on current beta (51), does this happen on 49 only? Can you try current stable version? 51 or above?
,
Jun 3 2016
I was on the current stable (50) and it still happened on that. So i switched to the beta channel (52.0.2743.24) and was able to successfully install two different extensions. It appears the problem is resolved in beta. At least for me. Thank you!
,
Jun 4 2016
Thank you for providing more feedback. Adding requester "lazyboy@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
,
Jun 7 2016
I tried reproducing it in 50.0.2661.0 mac, but no luck. @3, If you can reproduce this, open a new tab and type chrome://crashes and see if there's a crash id at the time you are experiencing this. You'd see crash entries that start like this: "Crash ID xxxxxxxxxxx", you can provide the crash id here and ping the bug if you can find it.
,
Jun 7 2016
There must be something very specific to my environment that caused it (and the other commenter @1) as it doesn't seem widespread. When it did happen, it was a hard crash, essentially forcing a sudden reboot in the middle of checking the extension before installing. No option there to check for a crash report. After the reboot completed and logging back in, I did check for crash reports but found none. Since switching to the beta channel and experiencing no new crashes, I'm not aching to go back and try to reproduce this. As far as I'm concerned, this is resolved. I will wait until the current stable channel is on par with my beta channel version. Then I'll reinstall the stable channel. If it reoccurs after that, I'll make another comment here -- or just file a new issue and reference this one. |
||||
►
Sign in to add a comment |
||||
Comment 1 by wbart...@gmail.com
, Apr 5 2016