496652 - Sometimes a DOM Element returns a *very* large number from its 'length' property

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Scott Kyle]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)

This is very hard to reproduce.  An animation that I have on a page would sometimes cause an unresponsive script error.  After using the debugger forever to track it down, I found the problem in jQuery's makeArray function.  In it, it retrieve the 'length' property of the item, and wrongly assumes that a DOM element doesn't have a length, which is true pretty much all the time.  But *sometimes* a DOM element would return an **enormous** number, which I'd guess is from some sort of memory leak.  That would cause jQuery to loop with that number, causing an unresponsive script.  I'm sorry, I don't have a reduction.

Reproducible: Always

Steps to Reproduce:
Unable to consistently reproduce, seems to be from a memory leak
Actual Results:  
A gigantic number

Expected Results:  
Undefined

Comment 1

[Tyler Downer [He/Him]]

This is a mass search for Firefox General bugs filed against version 3.0 that are UNCO and have not been changed for 200 days.

Reporter, please update to Firefox 3.6.10 or alter. Firefox 3.0 is no longer supported and is no longer receiving updates. After you update, please create a fresh profile, http://support.mozilla.com/kb/managing+profiles, and test to see if your bug still exists. If you still the bug, then please post a comment with the version you tested against, and the problem. If the issue is no longer there, please set the RESOLUTION to  RESOLVED, WORKSFORME.

Comment 2

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.