Some time, when you open many tabs in Google Chrome, it will crashing .. We will show you how to fix crashing google chrome in Windows 10 easy.
How to fix crashing Google Chrome for multiple Windows 10
Google’s Chrome browser update reportedly had a bug that caused major problems for Windows 10, resulting in the browser closing completely and extensions randomly crashing.
According to Windows Latest, the Chrome 90 update had a bug that had been crashing Google’s browser for Windows 10 users. Fortunately, the issue did not appear to be affecting those who use macOS.
One of our writers started experiencing the issue on Wednesday, May 20, when several notifications appeared saying all the browser’s extensions had crashed. Along with this, blank pages appeared when going to any website (as shown below).
Other Chrome users have been experiencing similar issues, with extensions, settings pages, and tabs crashing completely. Users have also experienced the Chrome browser refusing to launch altogether.
How to fix crashing Google Chrome on Windows 10
Google released an update for Google Chrome users, including for Windows, Linux, and Chrome OS, in order to resolve the issue.
For Windows devices, be sure to close any open Chrome windows and then re-open Chrome. Keep the Chrome browser open for about five minutes, then quit Chrome and then relaunch it once again. As Google notes, the behavior should be resolved.
For those experiencing problems on Linux devices, navigate to the directory containing the Chrome user profile via .config/google-chrome/. From here, delete the contents of the [Chrome user profile] Origin Trials subdirectory, which should include a “188.8.131.52” directory.
Then, delete the [Chrome user profile] Local State File, and then start Chrome again. Google states that it should load as normal.
Finally, for those impacted on Chrome OS devices, such as Chromebooks, Google has provided a help page to cover various problems multiple users may be experiencing.
Update on Wednesday, May 26: Google identified the cause of the issue and released an update that resolves the bug. What follows is an updated article and a solution for Windows, Linux, and Chrome OS users to receive the update.
Read more :