A common cause for Chrome to crash during startup is running Chrome as root user. If your issue only occurs in a special, uncommon testing environment, be aware that the ChromeDriver devs may choose not to investigate/resolve your issue. This Tutorial Will Help You Fix The Following Issues:Google Chrome Not Working. This often fixes problems if you are running Selenium as a background service.
#GOOGLE CHROME NOT RESPONDING ON STARTUP HOW TO#
If none of these solutions fixes the problem, file a new issue with instructions on how to reproduce the problem. Again, make sure to sync your browsing data to a Google Account before you go. That reverts all browser settings and allows you to start using Chrome in a new state. If you still keep running into frequent Page Unresponsive errors, it’s time to reset Google Chrome. Please configure your environment to run Chrome as a regular user instead. Sign in with your Google Account to start using it. While it is possible to work around this issue by passing '-no-sandbox' flag when creating your WebDriver session, such a configuration is unsupported and highly discouraged. This often fixes problems if you are running Selenium as a background service.Ī common cause for Chrome to crash during startup is running Chrome as root user (administrator) on Linux. Otherwise, if the problem only occurs in your special testing environment: If your test exhibits the same problem even in a simple testing environment, file a new issue with instructions on how to reproduce the problem. Google has figured out whats been causing so many Chrome 78 users to see the.
212 on May 10th, and for the most part, there. You can get a report on this by typing chrome://crashes into your omnibar. If this doesnt work, contact the website owner and let them know youve been having problems loading the webpage.
#GOOGLE CHROME NOT RESPONDING ON STARTUP WINDOWS#
For example, in Java, you may use the ProcessBuilder API to start the Chrome binary directly. Google Chrome has suddenly started crashing yesterday for many Windows users worldwide making the browser unusable. First, try restarting your modem and router. You should also check that you are able to launch Chrome directly from your test (without using WebDriver/ChromeDriver). If Chrome fails to start correctly, you need to fix your installation of Chrome (perhaps by re-installing).Īssuming you are able to run Chrome from a command prompt, your next step should be to see if the same problem occurs when running your test in a simple testing environment (preferably launching the test binary/script directly from a normal user's command prompt). If you are passing any special command line switches/arguments to Chrome, make sure to include those too. This often happens when running ChromeDriver/Chrome using a special test harness (perhaps an IDE) or continuous build system (e.g., Jenkins).įirst, try launching the same Chrome binary that your test uses from a normal user command prompt (check your chromedriver.log file to see what Chrome is being used).