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. Outliner identifies these windows as having been subject to a Chrome/Chromium crash however - so they *are* crashing, in some sense.Chrome is normally a very stable browser, reliable and easy to use. And at login again when my sessions are restarted there's no mention of a crash, no option to (not) re-open the previous tabs & windows - so it just goes ahead and re-opens them all. I mean that during shutdown there's no warning of them crashing. When Chrome and Chromium restart I don't get the option to not re-open closed windows - as far as they are both concerned there was no crash at the last shutdown.
)Īs you say it's a bit more complex, though, and I guess part of it will be tracking subtle changes to what a collection of tabs (window) could be while still considering a window of tabs to be the *same* as another window of tabs.īut, yes, in the very short term, just the option to drop all the crashed windows (without having to collapse them in the outliner view) would be really fantastic - and I naively hope this would be relatively easy to implement, and sufficiently useful to others. I do try to not duplicate existing bug/wishlist items.
I did search through the out-standing wishlist items, and indeed the 'match up existing windows with crashed windows - and if they exist, don't create a 'crashed' version' - that'll be great when it's done. Ah, yes, my apologies, I should have been clearer.
0 kommentar(er)
