76622 - Limit in appending elements in DOM not handled very well, possible memory leak

Status: RESOLVED DUPLICATE of bug 58917

(Core :: DOM: Core & HTML, defect, P5)

Description

[Vladimir Ermakov]

When appending elements in dom once you append above 196 nested elements there 
is a problem. Whatever you appened to the "deepest" node doesnt render. At first 
I thought that this was a boundry value, the limit for nesting, but then I 
noticed that the more elements you append the longer it takes to process it. 
If you append 200 elements it will take a second, if you append 1000 it will 
take a minute. But the result is stil the same - nothing. In IE however it is 
much faster, and you can still see the last appended element no matter how 
deep you are in the tree, even if it is 1000 elements. I dont know if the 
elements are actualy generated, and are just not rendered. What happens to those 
that are appended after 196? is there a memory leak?
 To reproduce open the attachment. Tag field is the name of the tag that you 
want to create, and depth is how deep you want to nest it. Then click Generate 
Test, and a "CLICK HERE" message should appear. If you click on it it will call 
event handlers attached to each tag as it is created and will output the tag's 
id. Put in different values like 196, 197, 300, 500... and see how it behaves.

Comment 1

[Vladimir Ermakov]

Attachment: testcase

Comment 2

[Johnny Stenback (:jst)]

"Don't do that then" :-)

Should probably be fixed, but not critical now.

Comment 3

[Prashant Desale]

Updating QA contact to Shivakiran Tummala.

Comment 4

[Johnny Stenback (:jst)]

Mass-reassigning bugs to [e-mail]

Comment 5

[Boris Zbarsky [:bzbarsky]]

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