[Webkit-unassigned] [Bug 87433] New: Safari Web Content crashes have pessimal recovery characteristics

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu May 24 15:08:09 PDT 2012


https://bugs.webkit.org/show_bug.cgi?id=87433

           Summary: Safari Web Content crashes have pessimal recovery
                    characteristics
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Macintosh Intel
        OS/Version: Mac OS X 10.7
            Status: UNCONFIRMED
          Severity: Major
          Priority: P1
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: fabian at mailinator.com


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.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list