Closed Bug 588219 Opened 14 years ago Closed 14 years ago

An alert window puts Firefox in an endless loop

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 622326

People

(Reporter: mfried, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.2 Firefox/3.6.8
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.2 Firefox/3.6.8

If a page contains an element with style = 'position : fixed'
and that page starts a JavaScript alert()
then when the page is loaded the alert window is empty and Firefox goes into a loop.


Reproducible: Always

Steps to Reproduce:
1. Load page
2. Wait for Alert window to appear. Keep an eye on CPU usage.

Actual Results:  
Firefox loops and an Alert window appears without content.

Expected Results:  
Alert with content.

Here is the HTML I used:

<html>
    <body
        onload     = "onLoad();">
        <script>

            function onLoad(){
            
                alert('bob')

            }
        </script>
    
        my html text

        <div
            style = 'position : fixed;
                     top      : 10px;
                     left     : 10px'>
            bob
            bob
        </div>

    </body>
</html>
Tried it on Windows XP with FF 3.6.13 without problems.
Tried it on FF 3.6.2 on OpenSUSE 11.2 without any negative effects.
Maaaaaybe bug 622326 wrt the CPU usage? I see the CPU spike on my Windows 7 box when I enable window-modal prompts. It also seems that we don't paint the prompt's contents until I move the mouse over the prompt's window, which is odd.

But everything seems to work fine when using the (new, default) tab-modal prompts.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Yeah, this is almost certainly bug 622326. Top of the stack when the CPU is burning is nsGlobalWindow::ReallyClearScope
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.