New issue
Advanced search Search tips

Issue 818553 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome doesn't launch, crashes repeadtedly

Reported by okk...@gmail.com, Mar 5 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299

Steps to reproduce the problem:
1. REBOOT Windows 10 (consistently happens on reboot)
2. Try to launch Chrome
3. Chrome crashes and doesn't launch

Additional information:

- Delete the Chrome folder in AppData\Local\Google. 
- Chrome launches once. 
- Close Chrome
- Try to re-launch.
- Chrome crashes and doesn't re-launch

What is the expected behavior?
Chrome should launch!

What went wrong?
Attaching the dmp file from: 
AppData\Local\Google\Chrome\User Data\Crashpad\

Crashed report ID: No

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Chrome version: 64.0.3282.186  Channel: stable
OS Version: 10.0
Flash Version: 24.0.0.189 internal-not-yet-present

I have been using chrome on Windows 10 on my current PC for over 4 months now. This issue is happening since 2 weeks.
3rd party add-ons installed:
XMarks
AdBlockPlus
OneTab

However, I believe add-ons has nothing to do with the crash.
On deleting the AppData\Local\Google\Chrome folder and restarting, there are no add-ons, but Chrome still crashes.
 
Crashpad.zip
149 KB Download
Cc: jmukthavaram@chromium.org
Labels: Needs-Feedback Needs-Triage-M64
Thanks for the report with details.

Unable to reproduce the issue on Windows 10,Mac 10.13.3 using chrome reported version-64.0.3282.186,latest stable-65.0.3325.146	& Canary-67.0.3362.0.	

Could you please try to uninstall chrome once & reinstall latest stable from the below link on Windows 10 & please check the issue with clean profile without any apps and extensions.Once chrome issue get resolved,try to add required extensions & let us know your observations on the same.

https://www.chromium.org/getting-involved/dev-channel

Thanks..!


Comment 2 by okk...@gmail.com, Mar 8 2018

Does deleting everything "chrome" from the Users/<user>/AppData count as clean profile? I am doing that now to check.
Project Member

Comment 3 by sheriffbot@chromium.org, Mar 8 2018

Labels: -Needs-Feedback
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

Comment 4 by okk...@gmail.com, Mar 8 2018

Here is what I followed:
1. Uninstall current version of Chrome(64.x.xxxx.xxx)
2. Delete anything that matches Chrome in /Users/<user>/AppData folder
3. Install Chrome (65.x.XXXX.XXX) from the link given.
4. Reboot the PC
5. Launch chrome
Result: Chrome crashes, with the same symptoms. 

Attached is the crash dump files, again.

Chrome version: 65.0.3325.146 (Official Build) (64-bit)


reports.zip
433 KB Download

Comment 5 by okk...@gmail.com, Mar 8 2018

Additional Info: 
I just ran a memory check on my PC to see if there are any hardware issues resulting in the crash (like corrupt memory module etc.,). Lucky for me, the memcheck returned no errors. 
Cc: kkaluri@chromium.org
Components: UI
Labels: Needs-Feedback
okkhoy@ Could you please help with the 16 digit crash id from chrome://crashes for further triage.
818553.png
24.2 KB View Download
Same happens on my Windows 10 since Chrome Dev 66.0.3359.22.
Canary works.
Earlier Dev versions wouldn't crash, but fail to reopen the last opened tabs after Shutdown->PowerOn cycle. This time the blank browser window opens but before I manage to do anything it crashes.

Comment 8 by woxxom@gmail.com, Mar 11 2018

re 66.0.3359.22 it's a duplicate of  issue 816628 .
Try right-clicking chrome.exe and setting the compatibility mode to Windows 7 or 8 until you get the new fixed update.
Status: Archived (was: Unconfirmed)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment