Setting innerHTML prior to adding a node to the document crashes Firefox




13 years ago
13 years ago


(Reporter: daniel, Unassigned)


Firefox Tracking Flags

(Not tracked)





13 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

To reproduce this you'll need to have the Greasemonkey extension running and
install a modified version of my Wikipedia Animate script (available at the URL
listed above). Once you have it installed, simply click the "Animate" button
from a Wikipedia history page.

Line 360 is where things go bad:

        // The following should crash Firefox 1.0.4
        frame.innerHTML = content;
        main.insertBefore(frame, controls);
        /* This will not crash Firefox
        main.insertBefore(frame, controls);
        frame.innerHTML = content;

Sorry about having such a complex test case, but so far I haven't been able to
reproduce it with anything simpler.

Reproducible: Always

Steps to Reproduce:
1. Install Greasemonkey
2. Install Wikipedia Animate user script
3. Visit a Wikipedia article history page
4. Click the animate button

Actual Results:  
Spinning beachball of death, followed by a crash notification.

Expected Results:  
Animation of the Wikipedia article revision history.
Can you reproduce this crash also in a nightly trunk build?
Also, do you have a talkback ID number from the crash?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.