Bug 8588

Summary: processor usage goes high for 30-200 seconds when viewing digg items
Product: WebKit Reporter: tim bates <timothy.c.bates>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Major    
Priority: P2    
Version: 420+   
Hardware: Mac   
OS: OS X 10.4   
URL: http://www.digg.com
Attachments:
Description Flags
sample taken during a lock up of safari processing digg none

tim bates
Reported 2006-04-25 18:06:28 PDT
Hi, digg is a popular site using AJAX to allow comment folding, and other usability features. Viewing digg articles, especially opening a few at once in new tabs locks up safari (Spinning Wheel of Death) and pushes processor usage to 80% or so for 30-200 seconds (on my single processor powerbook G4). I attach a sample taken during one of these lock-ups. they always resolve, and the pages then work fine until a reload event.
Attachments
sample taken during a lock up of safari processing digg (81.08 KB, text/plain)
2006-04-25 18:07 PDT, tim bates 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
tim bates
Comment 1 2006-04-25 18:07:32 PDT
Created attachment 7965 [details] sample taken during a lock up of safari processing digg
Dave Hyatt
Comment 2 2006-04-25 19:25:56 PDT
I believe this is digg's fault (i think this is a dup). Something about us handling onload correctly but Firefox being buggy, so we exec a ton of JS.
Alexey Proskuryakov
Comment 3 2006-04-26 05:37:46 PDT
*** This bug has been marked as a duplicate of 7657 ***
Note You need to log in before you can comment on or make changes to this bug.