Closed Bug 278005 Opened 20 years ago Closed 19 years ago

infinite loop, when iframe is created in framed page.

Categories

(Firefox :: General, defect)

PowerPC
macOS
defect
Not set
minor

Tracking

()

RESOLVED EXPIRED

People

(Reporter: gnebulon, Assigned: bugzilla)

References

()

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a6) Gecko/20050111 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a6) Gecko/20050111 Firefox/1.0+

In a page that has frames on it, using javascript to create an iframe causes
mozilla to enter into some sort of an infinite loop.  It says "Loading..." and
the wheel keeps circling.  It hits the CPU harder.  

Other than that, everything seems to work.  The rest of the JS on a page, the
browser interface, ...  It just goes into some sort of an infinite loop.

This only happens if the iframe is created in the onload function, or a function
called by it.  Therefore, a good workaround is to call the iframe-creating
function with a setInterval of 0ms.

Reproducible: Always

Steps to Reproduce:
1.  In a page inside of a frameset, create a funciton to be called with the
page's onload.  Let's call that function init()

2.  Have init() create an iframe (with any src) and attach it to the body. 

Actual Results:  
The title of the page is always "Loading..." and the little circle keeps on
moving around.  It hits the CPU harder, evidently in an infinite loop.

Expected Results:  
Recognized that it has finished loading the page, and quit drawing CPU resources.
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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.