Google Chrome has suddenly started crashing yesterday for many Windows users worldwide making the browser unusable.
Google released Chrome 90.0.4430.212 on May 10th, and for the most part, there have been no reported issues with the release until yesterday.
As first reported by Windows Latest, starting yesterday morning, users began reporting that Google Chrome extensions and tabs suddenly began crashing while using the browser.
Due to these crashes, the Chrome subreddit and Chrome product forums have begun filling up with posts from people experiencing these issues.
"Seemingly out of nowhere ~15 minutes ago, Google Chrome stopped working for me. My extensions crashed and all pages (including Chrome pages like settings) refuse to load. The screen is completely blank, and the tab is simply labeled "Untitled" with a frowning folder next to it," a user posted yesterday to Reddit.
While BleepingComputer has not experienced these crashes, users report that Chrome is displaying a gray screen and cannot open the Settings or Extensions pages of the browser.
Furthermore, users are reporting that these crashes happen in both the regular and Incognito browsing modes.
It is believed that the crashes are caused by an issue with the Google Chrome '%UserProfile%\AppData\Local\Google\Chrome\User Data' folder, which is used to store your data, extensions, and configuration settings for the browser.
A Google Product Expert recommends that users create a backup of the 'User Data' folder and then perform one of the following steps to fix the crashes:
As this only seems to be happening on Windows I will provide such instructions, but this will be operating system dependent:
- Ensure your Sync data is accurate at https://chrome.google.com/sync and passwords appear at https://passwords.google.com (If you have a passphrase they will not but they should be reflected in the sync data link)
- Close any open Chrome instance
- Open File Explorer and navigate to:
%LOCALAPPDATA%\Google\Chrome\User Data
- Delete the "
Local State
" file from the directory (ensure you have a backup!)- Re-Open Chrome
If the above steps don't resolve the problem then try the following
- Open File Explorer and navigate to:
%LOCALAPPDATA%\Google\Chrome\User Data
- Take a copy of everything in this directory and store it somewhere such as your desktop
- Rename the "
User Data
" folder to something other than User Data- Re-Open Chrome
Some users have reported that after performing these steps, the Google Chrome crashes have stopped.
Others state that once you restart Google Chrome the issue occurs again.
It is not clear what is causing the crashes, but it is likely a change pushed out to some users by Google since the latest browser release.
It is common for Google to push out configuration changes or new features to Google Chrome users in limited tests. One of these tests or configuration changes may be causing the issues seen by so many users.
Update 5/23/21: Google has shared the following fix that can be used to resolve the crashes:
For impacted Windows devices follow these steps:
Quit any open Chrome windows.
Re-open Chrome. You will still see the broken behavior.
Keep Chrome open for about 5 minutes.
After 5 minutes quit Chrome and then relaunch Chrome. The behavior should be resolved.
For impacted Linux devices follow these steps:
- Navigate to the directory containing the Chrome user profile:
.config/google-chrome/
- Delete the contents of the
[Chrome user profile]
\Origin Trials subdirectory
- This should include a "1.0.0.7" directory
- Delete the
[Chrome user profile]
\Local State file
- Start Chrome, which should load as expected
Comments
BilliamJ - 2 years ago
Just dealt with this earlier today, one of our Administrators had it happen, after fighting with it for a while I backed up and then deleted the User Profile folder and let Chrome create a new one, luckily she only had a few bookmarks.
Mike_Walsh - 2 years ago
What can I say? No issues with Chrome under ANY of multiple Linux distros.....
modelsupplies - 2 years ago
They roll changes out to small groups of users at a time. You got lucky this time.
opera - 2 years ago
I can just imagine some poor users trying to find appdata folder when their hidden files and folders are not set to show.
ProTruckDriver - 2 years ago
What can I say also. No issues with Chrome and my Mac computer.
Drakkaar - 2 years ago
Hey, I came across this issue with a user's computer today and came across a Reddit post that explained the fix. The fix should work and save anyone from having to worry about backing up their User Data.
This is caused by Origins Trials Component version 1.0.0.7. Here is how to fix:
Open manifest.json in %localappdata%\Google\Chrome\User Data\OriginTrials\1.0.0.7
Removes contents of signatures
"disabled-tokens" : {
"signatures" : [ ]
}
Save file and relaunch browser twice.
Hope this helps!
Lawrence Abrams - 2 years ago
Any chance you have the original contents of the manifest.json that is causing the problem?
modelsupplies - 2 years ago
This didn't work for me, either, though I saw both of these fixes working for some on Reddit.
I just got a nice, new HP computer and now this. My whole business is run on Chrome. It's devastating.
Drakkaar - 2 years ago
Unfortunately not, I made the changes on the user's computer and they got it back same day, but I did not keep a copy of their unedited version.
On my work computer I have not yet updated Google Chrome to get the error, my OriginTrials folder still displayed the previous 1.0.0.6 version.
I can check if I can get the error to occur on my Home PC and look at uploading a copy if it happens.
modelsupplies - 2 years ago
I'm currently trying to get it to restore to a previous version, however, I think it's the same version. It's all I have left in my arsenal.
modelsupplies - 2 years ago
It worked! Restore to previous.
modelsupplies - 2 years ago
It worked! Restore to previous.
hoverdave - 2 years ago
To add to the article, if you're not using Chrome's sync feature mentioned above, you can copy the 'Default' subfolder of the backed-up User Data folder back to its original location and it will still work. Sauce: Happened to me also two days ago :)
jmiac - 2 years ago
I am having similar problems with Firefox; perhaps a hundred crashes in the last few days.