Windows 10 Anniversary Update breaks stable channel Chrome
Reported by
benj...@gmail.com,
Aug 23 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393 Steps to reproduce the problem: 1. Start Browser 2. See Window 3. Extensions Crash 4. Browser unusable What is the expected behavior? What went wrong? Browser is unusable Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? N/A Chrome version: 51.0.2704.79 Channel: stable OS Version: 10.0.14393 Flash Version: Shockwave Flash 22.0 r0 Chrome Canary works Maybe related to: https://bugs.chromium.org/p/chromium/issues/detail?id=522201# ?
,
Aug 24 2016
Hi! I can't give you those details because Chrome will keep crashing and does not show any other page than the one I have in the screenshot. EMET is disabled, Extensions are disabled (at least they do not visibly crash and are not visible in the Chrome window). The behavior is pretty much the same as the one in the linked issue and it started happening immediately after I installed the anniversary update for Windows 10. As I said, Canary works, but I want to stay on the stable branch. Best, Benedikt
,
Aug 24 2016
Also: I'm using the 64bit versions of Chrome
,
Aug 29 2016
,
Aug 29 2016
I'm pretty sure this is not an issue with the extensions, since everything worked fine before the update and using canary with the same account (everything is synced with Google) will lead to no crashes at all. I assume the versions of the extensions are the same as on my other installation.
,
Sep 2 2016
If Canary works, try performing a full restart of Windows (from a command prompt, run "shutdown.exe -r"). If the Stable build starts working magically after this reboot, this is a dupe of https://bugs.chromium.org/p/chromium/issues/detail?id=604149
,
Sep 4 2016
@elawre: Sadly a clean shutdown through the commandline did not help.
,
Sep 4 2016
after updating through the google setup to version 53.0.2785.89 m (64-bit) it got fixed
,
Sep 4 2016
same issue here. EMET 5.51 (latest) workaround: Turning EAF+ for chrome.exe help to avoid issue. waiting for fix. thanks
,
Sep 4 2016
#9 In general, we do not recommend the application of EMET to Chrome; it had caused issues in the past (https://www.chromium.org/Home/chromium-security/chromium-and-emet) and there are a few bugs on incompatibilities still active. #1 indicates his issue is fixed in the current version, so closing this out. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ranjitkan@chromium.org
, Aug 24 2016Labels: Needs-Feedback