Chrome crashes on start after upgrade to 53 from 52
Reported by
maji...@gmail.com,
Sep 2 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36 Steps to reproduce the problem: 1. Update chrome from 52.x to 53 2. Chrome starts to launch but gets an error 3. Browser opens to a bare bones screen where nothing runs What is the expected behavior? Chrome will launch successfully What went wrong? Chrome was running fine and the browser was closed. During this time, chrome was auto updated to the 53 version (up from 52) and it wouldn't start. When you launch the program, you get an unknown software exception (oxc0000409) occurring in a random location of memory. (as seen in chrome1.png) After you hit, ok the browser will load, but you're on the "Aw, Snap!" page and nothing will load. (not the settings, crashes, plugins, anything) I attempted to load chrome.exe --safe-plugins and the same thing happened. I removed chrome and re-installed chrome 52.0.2743.116 and it is working again for the moment. (I auto-updated again to verify and the same thing is happening) I'm currently back on 52.0.2743.116 and working, but not sure for how long. Crashed report ID: No, none exist How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? Yes 52.0.2743.116 Chrome version: 53.0.2785.89 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 22.0 r0 I'll watch the thread today to try and troubleshoot when I can if required.
,
Sep 3 2016
As stated in the original posting: "I removed chrome and re-installed chrome 52.0.2743.116 and it is working again for the moment. (I auto-updated again to verify and the same thing is happening)" No malware on system. Would have been detected by palo alto firewall or mcafee antivirus or mcafee host instrusion or snort IDS.
,
Sep 3 2016
>"I removed chrome and re-installed chrome 52.0.2743.116 and it is working again for the moment. (I auto-updated again to verify and the same thing is happening)" That leads me to believe that your computer is probably infected with malware. >No malware on system. Would have been detected by palo alto firewall or mcafee antivirus or mcafee host instrusion or snort IDS. McAfee in particular has poor malware detection rates. Furthermore, no antivirus or security solution (even a good one) has 100% detection rates at all times. There is still a possibility of a malware infection. I would try to *update* McAfee to the latest version and run a 'Full Scan' as well as run a threat scan with the latest version of Malwarebytes Anti-Malware.
,
Sep 3 2016
if I wasn't the guy that managed the epolicy orchestrator server, the ids, and the palo alto, i'd potentially agree with you. it's not malware.
,
Sep 3 2016
Do you have any error dumps or reports to provide?
,
Sep 3 2016
Unfortunately, the only thing that it ever created (no crash reports in the crash reports folder) is one of the times, it did create a WER but I wasn't 100% sure that it was created by the same issue.
,
Sep 3 2016
If you still have it around, could you provide it?
,
Sep 3 2016
(If you don't want to post it publicly for some reason feel free to email me.)
,
Sep 3 2016
It should still be there. I'll grab it (and cleanse if necessary) and send it when I can.
,
Sep 6 2016
So I am in front of the machine having the issue. There wasn't a WER, so I did several uninstall/reinstalls and even deleted the google folder from my appdata. (deleting all of my profiles and settings) I finally got it to create a WER and hopefully it will assist.
,
Sep 6 2016
FWIW, I'm starting to see this upgrade (automatically) across the enterprise with the exact same error on other machines.
,
Sep 8 2016
This is only seen on the x64 version of Chrome. I have been replacing it with the x86 on the user machines. Not a great solution, but removes the work stoppage.
,
Sep 11 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by lemoncustompc@gmail.com
, Sep 3 2016