RESOLVED CONFIGURATION CHANGED 87433
WebProcess crashes have poor recovery characteristics 
https://bugs.webkit.org/show_bug.cgi?id=87433
Summary WebProcess crashes have poor recovery characteristics
Fabian Mailinator
Reported 2012-05-24 15:07:14 PDT
Suppose you had 27 youtube videos pages open (and not playing) in 27 different windows. This seems to be enough to trigger a Safari Web Content crash. (Or even if it's not, sooner or later Safari Web Content is going to crash because that's what it does best.) When the inevitable crash of Safari Web Content happens, the system attempts to restart Safari Web Content. And that's where the fun begins. Safari Web Content, for reasons that appear to make no sense at all, ATTEMPTS TO RELOAD EVERY SINGLE PAGE IT HAD OPEN. ALL AT THE SAME TIME. Whatever thinking went into choosing this behaviour is clearly pretty faulty thinking. BECAUSE EVERY SINGLE ONE OF THOSE YOUTUBE VIDEOS BEGINS PLAYING SIMULTANEOUSLY. AND THERE IS NO WAY TO STOP THEM. And if having 27 open videos was enough to cause Safari Web Content to crash in the first place, IT CRASHES AGAIN! AND RELOADS EVERYTHING AGAIN! AND CRASHES AGAIN! As you can imagine, this behaviour does not lead to the most pleasant customer happiness. Since there's no way to prevent Safari Web Content from blowing its brains out of its ears every few hours, how about changing the recovery behaviour to only reload pages on demand? Or setting a flag that tells youtube to not begin playing. Or something. Anything.
Attachments
Add attachment proposed patch, testcase, etc.
Brady Eidson
Comment 1 2012-05-25 11:29:38 PDT
Part of this might be decisions WebKit2 makes, which we could look at here. Part of this might end up being decisions Safari makes, which is invalid to report here as they're outside the prevue of the WebKit Open Source Project I'd suggest you file a bug report at bugreport.apple.com to make sure all of your bases are covered.
Brady Eidson
Comment 2 2012-05-25 11:34:55 PDT
(In reply to comment #0) > Since there's no way to prevent Safari Web Content from blowing its brains out of its ears every few hours Also, if you are seeing frequent and/or reproducible crashes in the WebProcess, you should be filing good bugs on those. If you're under some conviction that we don't like identifying, exploring, and fixing crashing bugs then you are poorly mistaken.
Ahmad Saleem
Comment 5 2022-08-06 16:18:42 PDT
Webkit2 resolved lot of these issues and now there are quite advancement in crash handling of bugs and crashes are on per-level. Since Safari has evolved a lot and Webkit as well. I am going to mark this as "RESOLVED CONFIGURATION CHANGED". If this is incorrect, please mark accordingly. Thanks!
Note You need to log in before you can comment on or make changes to this bug.