Bug 22095 – Worst seizing up of Webkit I've ever seen.

• Status: RESOLVED
• Resolution: INVALID
• Component: New Bugs

[CWG]

Opening that URL in Webkit results in a page opening with a series of warning messages that apparently continue endlessly, resulting in the worst memory paging and unresponsiveness from a Mac I have ever seen.  It stops the system clock display from updating, spinning beachball everywhere on the screen.  If the Finder can be gotten to, Force Quit will not come up.  The only way I could get out of it was the power button.

[Mihnea Ovidenie]

(In reply to comment #0)
> Opening that URL in Webkit results in a page opening with a series of warning
> messages that apparently continue endlessly, resulting in the worst memory
> paging and unresponsiveness from a Mac I have ever seen.  It stops the system
> clock display from updating, spinning beachball everywhere on the screen.  If
> the Finder can be gotten to, Force Quit will not come up.  The only way I could
> get out of it was the power button.
> 
Hello,

Have you tried to open that URL with other browsers? Using curl to access it, it just gets the following errors over and over again:

<b>Warning</b>:  fgets(): supplied argument is not a valid stream resource in <b>/home/pojarnik/domains/learnyouself.com/public_html/index.php</b> on line <b>21</b><br />
<br />
<b>Warning</b>:  feof(): supplied argument is not a valid stream resource in <b>/home/pojarnik/domains/learnyouself.com/public_html/index.php</b> on line <b>21</b><br />

Might be a broken page, why do you think it is a WebKit issue?
Regards,
Mihnea

[Alexey Proskuryakov]

I think that the browser becoming completely unresponsible should be treated as a bug regardless of how broken the page is - especially if the browser takes the whole system with it! But yes, it is important to compare the behavior with other browsers, as well.

Depending on details, this may end up being treated as a WebKit or Mac OS X bug, or even both.

(disclaimer: I didn't attempt to reproduce this).

[CWG]

Hi,

I tried it twice in FireFox v. 3.0.3.  The first time it came up immediately with a simple 3 line dialog to the effect that the site was home to many sites, and should be accessed via those sites, with no apparent probs.  The second time, it displayed the same error messages which Webkit does, but, apparently, without the massive memory paging Webkit experiences.

Firefox's, as well as the System's, responsiveness did slow, but it did not become completely unresponsive.  Webkit would not respond at all to "Command - period" to stop the page loading, in any of the three accesses I made to the page with it.  Firefox did respond to "Command - period", stopped page loading, and I was able to exit the window normally.

[Background] this is the base domain of current Malware attacks on Yahoo! Answers.  Yahoo!'s handling of the attacks is a whole 'nother story, but, when suspect sights are seen, I, rather than a Windows user, open them up, to see what's what.  Webkit/Safari's reaction to this one is a severe blow to it's "reputation" among Windows users ;) .

[Mark Rowe (bdash)]

Did anyone save a web archive of the problematic page?  The URL does not load for me.

[CWG]

This may well have become moot, as the site has been reported to the host as a source of malware, and, evidently, shut down by the host.

Without the site, as it existed at the time, or a similar exemplar, Webkit's performance in the situation may be difficult to examine.

[Alexey Proskuryakov]

Perhaps we could reproduce this with a custom script that would dump endless content as pasted in comment 1.

[Brent Fulgham]

The 'learnyouself.com' website is no longer operational. We can't take further action on this bug.