100911 - wocs.com - Browser hangs when JS Strict warnings enabled.

Status: VERIFIED DUPLICATE of bug 78179

(Core :: JavaScript Engine, defect)

Description

[Henrik Gemal]

Try going to:
http://wocs.com
Mozilla becomes totally unavailable and you have to trash it!

build 20010920

Comment 1

[Gilles Durys]

wfm 2001092012 trunk mac and 2001092021 trunk linux

Comment 2

[Olivier Cahagne]

wfm using build 2001092003 on Win2k.

Comment 3

[Robert Rainwater]

wfm 2001092103 windows me

Comment 4

[jay garcia]

WFM Win98SE 2001092103, in view of all WFM's changing to INVALID

Comment 5

[Henrik Gemal]

Try turning on javascript strict warnings in the "Edit -> Prefs -> Debug" and 
then go to the site again...

Comment 6

[Olivier Cahagne]

Confirming on Win2k with build 2001092503 with Debug ticked.
I see many warnings about document.all so I guess this could be moved to Tech
Evangelism.
There's another bug about implementing a policy to avoid JavaScript loops
trashing Mozilla but can't remember of.

Comment 7

[Olivier Cahagne]

See bug 13350 to avoid JS loops.

Comment 8

[Asa Dotzler [:asa]]

->TE

Comment 9

[Bob Clary [:bc] (inactive)]

looks like danish or something similar to me... -> Europe West

Comment 10

[Tristan Nitot]

WFM in N62 on Win2K.
No messages in the javascript console.
same with 20011010 Moz build on linux.

The site has been fixed, I guess.

Marking Resolved fixed.

Comment 11

[Henrik Gemal]

Mozilla 20011112 become totally unavailable to a long time ½-1 min.

Please turn on javascript strict warnings in the "Edit -> Prefs -> Debug" and 
then go to the site again...

Comment 12

[Tristan Nitot]

Should we bother to evangelize a site that works fine unless the browser is in
debug mode w/ strict warnings... 
Setting P5. accepting bug.

Comment 13

[z-aillon.c-obsolete2]

Sending this to JS Engine people.  I don't think this an evang issue since we
load the page fine with strict warnings off.

Very noticable hang here with strict warnings on.

Comment 14

[z-aillon.c-obsolete2]

->JS Engine, could be DOM 0.

Comment 15

[Phil Schwartau]

This warning stands out. It repeats ad infinitum in the JS Console:

      Warning: reference to undefined property document.all
      Line: 81
      Source File: http://wocs.com

This is caused by the code below: window.onerror is set to a function
which itself produces a JS-strict warning. This causes the infinite loop -

window.onerror=reapply;
function reapply()
{
  setTimeout("slideit()",2000)
  return true
}

function slideit()
{
  if (!document.images)
    return
  if (document.all)  <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< LINE 81
  slide.filters.blendTrans.apply()
  document.images.slide.src=eval("image"+step+".src")
  if (document.all)
    slide.filters.blendTrans.play()
    whichimage=step
      if (step<number_of_images)
      step++
  else
    step=1
  if (document.all)
    setTimeout("slideit()",speed*1000+3000)
  else
    setTimeout("slideit()",speed*1000)
}

Comment 16

[Christopher Aillon (sabbatical, not receiving bugmail)]

So this is possibly a dupe of bug 13350 then.  The strict warning comes from the
test of document.all existing or not  but from what I can tell, it doesn't
really affect the page... They just have MS specific code which they hide by
enclosing it within the if blocks.

Is window.onerror supposed to be triggered for warnings as well?  Should this be
duped or sent back to evangelism?

Comment 17

[Phil Schwartau]

Note, too, the site authors define the above script in JS1.2:

           <script language="JavaScript1.2">

I don't know if this is a contributing factor as well. It seems that
this bug is DOM-related: what should the browser do if window.onerror
is a function which itself causes an error? 

Compare bug 13350:
"DOM needs to police JS infinite loops, schedule garbage collection"

Reassigning to Kenton; cc'ing Brendan to ask whether this is a dupe
of bug 13350 or is actually a JS Engine issue -

Comment 18

[Alex Vincent [:WeirdAl]]

This sounds like bug 81279 or bug 78179.

Comment 19

[Alex Vincent [:WeirdAl]]

:D I don't think you can get a bug which is much more of a dupe than this.  The
URL for this bug and the URl for bug 78179 point to identical pages... one is
clearly a mirror of the other.

Feel free to reopen if you disagree.


*** This bug has been marked as a duplicate of 78179 ***

Comment 20

[Henrik Gemal]

verified dupe