Bug 13597 - REGRESSION (419-522+) World of Warcraft Account Management causes WebKit to freeze
Summary: REGRESSION (419-522+) World of Warcraft Account Management causes WebKit to f...
Status: RESOLVED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 523.x (Safari 3)
Hardware: Mac (Intel) OS X 10.4
: P1 Critical
Assignee: Nobody
URL: https://www.worldofwarcraft.com/accou...
Keywords: InRadar, NeedsReduction
Depends on:
Blocks:
 
Reported: 2007-05-05 10:37 PDT by AJ
Modified: 2007-07-16 17:10 PDT (History)
0 users

See Also:


Attachments
WebKit Screenshot at point of "freezing" (822.92 KB, image/png)
2007-05-05 10:38 PDT, AJ
no flags Details
Safari (419.3) rendered version of the page. (404.24 KB, image/png)
2007-05-05 10:42 PDT, AJ
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description AJ 2007-05-05 10:37:15 PDT
After logging in to the WOW Account Management Area, the latest build begins to render the page. It gets to the point of "Loading...120 of 125" and then sits there, the address/tab bars showing that it is still attempting to load. WebKit must be force quit at this point.

Once it begins loading the page WebKit goes from <1% CPU to consuming an entire processor core (Core 2 Duo), and memory jumps from about 30MB to over 150MB within a few seconds, and then steadly climbs (more slowly) from there.

- The error does not occur in the Tiger-shipped WebKit that standard Safari uses (on my machine: v2.0.4 (419.3)).
- No Console output.
- Reproducible with the last few nightly builds (retrieved via NightShift.app).
Comment 1 AJ 2007-05-05 10:38:16 PDT
Created attachment 14360 [details]
WebKit Screenshot at point of "freezing"

WOW Username blurred out.
Comment 2 AJ 2007-05-05 10:42:55 PDT
Created attachment 14361 [details]
Safari (419.3) rendered version of the page.

WOW Username blurred out.
Comment 3 Dave Hyatt 2007-05-05 16:26:06 PDT
Raising to P1.
Comment 4 AJ 2007-05-08 15:58:34 PDT
Disabling JavaScript eliminates the lockup.
The main content loads fine, though the side (sitewide) navigation and some other peripheral elements do not load without JavaScript.
Comment 5 Oliver Hunt 2007-07-14 16:29:12 PDT
<rdar://problem/5335876>