REOPENED 102213
Hang of Safari Web Content process
https://bugs.webkit.org/show_bug.cgi?id=102213
Summary Hang of Safari Web Content process
lars.sonchocky-helldorf
Reported 2012-11-14 04:44:58 PST
The Safari Web Content process hangs forever when I view the above URL See attached sample
Attachments
sample of the situation (97.14 KB, text/plain)
2012-11-14 04:46 PST, lars.sonchocky-helldorf
no flags
lars.sonchocky-helldorf
Comment 1 2012-11-14 04:46:13 PST
Created attachment 174133 [details] sample of the situation
Alexey Proskuryakov
Comment 2 2012-11-16 13:28:25 PST
I cannot reproduce this with Safari 6.0.2 or current ToT.
lars.sonchocky-helldorf
Comment 3 2012-11-16 16:03:49 PST
I too can't reproduce it anymore. The given site changes constantly so the cause for this might have been gone. I regret no having saved a copy of the causing page … doesn't help the sample at least a bit?
Alexey Proskuryakov
Comment 4 2012-11-16 16:19:16 PST
This sample shows JavaScript doing a lot of work, so it might have well been a mistake in the script that caused an infinite loop of something equivalent. Sometimes, a sample can show WebProcess stuck somewhere, but not in this case.
lars.sonchocky-helldorf
Comment 5 2012-11-20 10:11:22 PST
This bug may not be easily or directly reproducible with the URL originally given in the report but it happens to me about 4 to 5 times a day when I surf sub pages of http://www.heise.de/ especially http://www.heise.de/newsticker/ and http://www.heise.de/newsticker/foren/ subpages that I get a lock up like the one reported: the Safari web content process goes to about 100% CPU and there is no way to stop this besides quiting and relaunching the WebKit nightly. This is also the reason I can't provide you with the HTML of the causing web page (since "show html source" is no longer working). I suspect it has something to do with the ads on this page. So this bug is not invalid but very real. Since heise.de is a major and highly respected german tech news site releasing Safari with this bug inside might cause trouble. Even if a JS infinite loop is the cause there should be a way to stop the hanging tab or window. Therefore I reopen this bug.
Note You need to log in before you can comment on or make changes to this bug.