Count your Chrome tabs and then check for Chrome processes in Task Manager. You can check that for yourself in Task Manager (Activity Monitor on Mac). Close tabsĬhrome typically runs each tab as a separate process. What if you can’t do either of those things, but you still need to get Chrome to work now?įind Chrome in your Start menu and right-click it, then select “Properties.” Find the target field and paste this text in at the end:Ĭlick “Apply,” and Chrome should work as normal when you relaunch it. If you can’t, consider using an Application Control Exception-this is likely to be the solution if you do have admin access to your Symantec account, but your OS is Windows Server 2016 or Windows 10 RS1 with any version of SEP installed. If you can, Symantec advises to upgrade to SEP 14.2 RU2 MP1 build. The solution is probably to update SEP from SEP 14.2, which many businesses have yet to do and which may not be in your control. SEP is very popular with business users, so if Chrome is crashing at work, this could well be the issue. Instead, it’s a problem with compatibility between the new build of Chrome and older versions of Symantec Endpoint security. Google has figured out what’s been causing so many Chrome 78 users to see the Oh Snap message. Update your endpoint security (or do this in the meantime) If there really has been a sudden uptick, it might be time to find out more.

This will show you a list of all the times Chrome crashed and when those crashes took place. But sometimes you’ll get a run of crashes, which can be frustrating.įirst things first: how often is Chrome crashing? You can get a report on this by typing chrome://crashes into your omnibar. Chrome is normally a very stable browser, reliable and easy to use.

Browsers keep crashing windows 10