Closed Bug 398086 Opened 17 years ago Closed 17 years ago

Attempting to view documentation on www.cisco.com results in browser hang

Categories

(Core :: JavaScript Engine, defect, P5)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: wgianopoulos, Unassigned)

References

()

Details

(Keywords: regression)

Attempting to view most documentation files on the www.cisco.com website results in the browser hanging for 10 full minutes, followed by the a script is not responding pop-up. This regressed somewhere between 1.9a7 and a.9a8. I will attempt to narrow this window.
Flags: blocking1.9?
This seems to be a regression from bug 392973 (verified by backout). It would appear there is someting wrong with the JavaScript that is looping here, but letting it go for 10 minutes before the pop-up occurs seems a bit much.
Blocks: 392973
Summary: Attempting to view doeumentation on www.cisco.com results in browser hang → Attempting to view documentation on www.cisco.com results in browser hang
Contact the site and point out the runaway recursion, if that's what is going on? /be
I was planning on debugging the script further to see what is going on, but I kind of thought the script not responding pop-up should have come up way before 10 minutes.
I think it is necessary to call the branch callback on inline calls in addition to to normal branches to allow stopping scripts before they consume 32M of the script stack space. But then better instruction counting from bug 364776 becomes important.
Depends on: 364776
Not convinced this one of 364776 should block, but Igor (or Brendan?) should make the call. I'm wildly guessing at P5 for both, if they do?
Priority: -- → P5
We need to investigate this more and figure out the branch-callback problem. Morph this bug or WFM it and open another?
Flags: blocking1.9? → blocking1.9-
In any event, evidently Cisco figured out their issue and I can no longer duplicate this issue on their website.
Calling this one WFM, though I wholeheartedly approve of improving the branch-callback situation, as per bug 364776.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.