Bug 12836 - Beachballing on digg.com comments
Summary: Beachballing on digg.com comments
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore JavaScript (show other bugs)
Version: 419.x
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL: http://digg.com/tech_news/Can_you_sur...
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-20 23:49 PST by Ted Wood
Modified: 2008-10-01 09:15 PDT (History)
1 user (show)

See Also:


Attachments
Sample file during hang (37.84 KB, text/plain)
2007-02-20 23:50 PST, Ted Wood
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ted Wood 2007-02-20 23:49:07 PST
As mentioned here by "josenintendo":
http://webkit.org/blog/?p=94#comments

My Safari v2.0.4 (419.3) hangs for a while during the loading of the referenced digg.com page.

I'll attach the Sample file once I figure out how
Comment 1 Ted Wood 2007-02-20 23:50:05 PST
Created attachment 13288 [details]
Sample file during hang
Comment 2 Ted Wood 2007-02-20 23:52:38 PST
PowerBook G4 1.5GHz, 2GB RAM, 10.4.8
Comment 3 David Kilzer (:ddkilzer) 2007-02-21 03:54:20 PST
Hi Ted!  Thanks for the bug report.  Could you try this with a WebKit nightly build to see if the issue still exists?  You don't need to install anything--just download the DMG, mount it, and run the gold Safari icon.  Thanks!

http://nightly.webkit.org/

Comment 4 Troy Brandt 2007-10-03 16:43:32 PDT
I can reproduce this in r25814. The only catch that I can see is that you must be logged in to get the hang. It seems to happen on any page with a lot of comments. 
Comment 5 Jonathan Field 2008-10-01 09:15:58 PDT
This is a hard one to reproduce, but if you cruise digg regularly, you'll run into it just about every day.  For me it doesn't quite beachball, but it uses about 70% of each CPU core.  It does not happen on every comment page.  It does not even happen on the same comment page every time.  Digg uses Ajax to retrieve comments, and it has rotating ads, so it could be either of those.

Closing the offending window brings everything back to normal.  I'll occasionally (but not always) get a "slow script" warning, which will also allow me to bring things back to normal.

Good luck, folks.  I tried to get a more reproducible case, but so far that has been fleeting.