RESOLVED WORKSFORME20123
REGRESSION: WebKit hangs consuming all CPU at junauza.com
https://bugs.webkit.org/show_bug.cgi?id=20123
Summary REGRESSION: WebKit hangs consuming all CPU at junauza.com
Dave English
Reported 2008-07-21 02:35:46 PDT
When I try to browse this web page, the browser hangs before finishing displaying it. The browser consumes all of a CPU, 50% of my dual CPU PC that is. I am running the nightly build r35130. I tried disabling plugins, just in case this was a flash player thing, but it still hung. If I browse using the regular Safari browser, 3.1.2 525.21 the page displays without a hang.
Attachments
Screenshot of Windows Task Manager to show 50% CPU usage (42.84 KB, image/gif)
2008-07-21 07:52 PDT, Dave English
no flags
Alexey Proskuryakov
Comment 1 2008-07-21 03:17:58 PDT
This doesn't happen for me with r35250 on the Mac.
Matt Lilek
Comment 2 2008-07-21 07:24:30 PDT
The page loads fine for me on Vista. In the latest nightly (r35130), it consumes around 50% CPU after it's loaded, but going to the home page and a couple other pages around the site, I barely see any CPU usage after it's loaded. In a local debug build of r35260, I don't see high CPU usage at all on any page.
Dave English
Comment 3 2008-07-21 07:51:36 PDT
Checking further, this only hangs on my dual CPU desktop, not my single CPU laptop. Processor usage sits just above 50% all of the time, so I suspected one was spinning. Looking at the Windows Task Manager, I see varying usage of both CPUs, but always above 50% & the browser is completely hung, it needs the safari.exe process to be ended. I will attach a screenshot of the taskman. The desktop machine is a Dell Precision WorkStation 670 with two 2.8GHz Xenon processors. The OS is XP SP3.
Dave English
Comment 4 2008-07-21 07:52:51 PDT
Created attachment 22403 [details] Screenshot of Windows Task Manager to show 50% CPU usage
Dave English
Comment 5 2008-07-28 07:22:07 PDT
Tis URL works without problem now in nightly build 35406
Robert Blaut
Comment 6 2008-07-29 00:05:05 PDT
(In reply to comment #5) > Tis URL works without problem now in nightly build 35406 > So the report can be closed now.
Note You need to log in before you can comment on or make changes to this bug.