Endless Loop: whoa google chrome has crashed relaunch now?
This reminds me why I switched to Firefox in the first place years ago. Oi.
Isn't it lame when a Google search for what appears to be a commonly-experienced problem does not have a solution which readily presents itself?
A search for "whoa google chrome has crashed loop" (or etc.) brings up a variety of results in the Google Product Forums--and kudos to all the good people that took the time to post, and repost, and follow-up, and try to help & collaborate. Regrettably, I couldn't find something that worked for me.
This page says to visit this page, and if that doesn't work...create a new user profile. Wait, what? Create a new Windows user profile? Madness! Mercifully no, the page is titled "Create a new browser user profile". Sheesh.
While searching to see if Chrome writes a log someplace, one nice person's article ultimately led me to stumble across the solution.
Here's what I found that works. Obvious disclaimer: use this at your own risk, I don't work for Google, and neither of us endorses the other; you are entirely responsible for your actions on your computer and in your life, just like the rest of us, etc. etc. etc.
Note that if "%LocalAppData%" doesn't work for you for whatever reason, e.g. because you and I are running different versions of Windows, consider performing a Google search for what the equivalent of %LocalAppData% is. In another web browser...
(In fact, for any given problem, computer or otherwise, try to use the same lingo as everyone else and ask Google. When in doubt, RTFM).
Good luck, fellow Chrome Crash Loop peoples!
Isn't it lame when a Google search for what appears to be a commonly-experienced problem does not have a solution which readily presents itself?
A search for "whoa google chrome has crashed loop" (or etc.) brings up a variety of results in the Google Product Forums--and kudos to all the good people that took the time to post, and repost, and follow-up, and try to help & collaborate. Regrettably, I couldn't find something that worked for me.
This page says to visit this page, and if that doesn't work...create a new user profile. Wait, what? Create a new Windows user profile? Madness! Mercifully no, the page is titled "Create a new browser user profile". Sheesh.
While searching to see if Chrome writes a log someplace, one nice person's article ultimately led me to stumble across the solution.
Here's what I found that works. Obvious disclaimer: use this at your own risk, I don't work for Google, and neither of us endorses the other; you are entirely responsible for your actions on your computer and in your life, just like the rest of us, etc. etc. etc.
- Navigate to %LOCALAPPDATA%\Google\Chrome\Application
- If you see something like "old_chrome.exe", continue...
- Rename chrome.exe to something else, e.g. "new_chrome.exe" (or bad_chrome.exe, or naughty_chrome.exe, you get the idea).
- Rename "old_chrome.exe" to "chrome.exe"
- Attempt to launch Google Chrome
Note that if "%LocalAppData%" doesn't work for you for whatever reason, e.g. because you and I are running different versions of Windows, consider performing a Google search for what the equivalent of %LocalAppData% is. In another web browser...
(In fact, for any given problem, computer or otherwise, try to use the same lingo as everyone else and ask Google. When in doubt, RTFM).
Good luck, fellow Chrome Crash Loop peoples!