RESOLVED WORKSFORME 11147
Safari freezes at symantec.com
https://bugs.webkit.org/show_bug.cgi?id=11147
Summary Safari freezes at symantec.com
Henk
Reported 2006-10-04 01:58:14 PDT
Goto: http://www.symantec.com/ Click on "products" At this point Safari freezes (uses almost 100% cpu time). It's fully reproducable on the two machines (PowerMacG5 DP 2.0Ghz, Intel iMac both running 10.4.8) I tried.
Attachments
Reduction of script execution order issue (1.60 KB, application/octet-stream)
2006-10-04 06:07 PDT, mitz
no flags
Not the patch for THIS bug. Ignore (3.26 KB, patch)
2014-04-03 15:35 PDT, Brent Fulgham
no flags
Henk
Comment 1 2006-10-04 02:08:46 PDT
Also reproducable with the latest nightly (r16763)
Alexey Proskuryakov
Comment 2 2006-10-04 05:21:45 PDT
http://www.symantec.com/script/20061003b/OmniScript_init.js: while( !( CheckVar( "window.OmniArray" ) ) ){} Sure enough, this freezes WebKit. Sounds highly related to bug 7722.
mitz
Comment 3 2006-10-04 06:07:36 PDT
Created attachment 10890 [details] Reduction of script execution order issue (In reply to comment #2) > Sure enough, this freezes WebKit. Sounds highly related to bug 7722. Indeed. In this reduction, the first time you open order.html, the execution order is 12. If you then open order.html in a new window, the order changes to 21. If you reload, it's 12 again.
mitz
Comment 4 2006-10-04 06:08:54 PDT
Changing to P2 since this isn't a regression and TOT has the hooks for terminating runaway scripts, so this isn't a freeze either.
Alexey Proskuryakov
Comment 5 2006-10-04 09:36:27 PDT
I suspect that Apple might want to fix this sooner than TOT ships... Adding HitListCandidate and NeedsRadar keywords, CC'ing Alice to prioritize this issue.
Stephanie Lewis
Comment 6 2006-11-08 16:01:44 PST
radar 4765923
Brent Fulgham
Comment 7 2014-04-03 15:35:39 PDT
Created attachment 228549 [details] Not the patch for THIS bug. Ignore
Brent Fulgham
Comment 8 2014-04-03 15:37:20 PDT
Uploaded a patch to this bug by accident. Nothing to see here.
Alexey Proskuryakov
Comment 9 2014-04-04 11:22:15 PDT
The site works for me now.
Note You need to log in before you can comment on or make changes to this bug.