383513 - New Window Freezes FF ( may be a result of new window call from I-Frame then main window )

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Nathan Winder]

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; WOW64; InfoPath.1; .NET CLR 2.0.50727; .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4

This bug occurs on win xp 64-bit. I am having other developers on our team test on other OSs and FF versions. We have an AJAX web application that emulates a windowed environment ( this is not its function rather a feature ). We use I-Frames to open other pages of our app in a main window. We use a new window popup to confirm or cancel a save request. The window is referenced using the same name in both the main window and the popup window. So If I open the i-frame and click save I get the popup and confirm, no problems ever. However, on occasion if I then press save in the main window the popup window appears the contents is solid white ( as in it cant repaint ) and FF freezes. Now this does not happen every time. As a result Im not even possitive of the cause. However, this sequence of events has yeilded the most freezes. I will continue to investigate as this effects our customers.

Reproducible: Sometimes

Steps to Reproduce:
1. create I-Frame
2. create new window popup with name "yourname" from within I-Frame
3. close new window popup ( do not destroy I-Frame )
4. create new window popup with name "yourname" from within main window
Actual Results:  
I have not tested using this exact sequence, rather this is the most likely sequence based on the way that our application works ( See "Details"). Unfortunatly I can devote only so much time exploring this bug as I have a long list of bugs to fix for our own application.

Expected Results:  
Fire fox should freeze. The popup window will be white as if unable to repaint. However, The main window while unresponsive does not go white.

FireFox should not freeze. It should also be noted that our application also runs in IE7 and has not exibited this bug. Also we have not seen this bug thus far so it leads me to believe that it was introduced in the latest release.

Comment 1

[Nathan Winder]

I did some testing using the admittedly simple "Steps to Reproduce" and I could not get the bug to fire. So clearly the issue is more complicated. It may be helpful to mention that the commit button in the new window popup kicks of an AJAX Soap request. However, the bug is occurring after the soap request has been returned from the iframe window. So I doubt that the request has anything to do with it. 

Comment 2

[Nathan Winder]

The IFrame is not the culprit. I can repeatedly open and close a new window and create the error. However, I could not repeat with the simple test procedure. Our application uses a window timeout to keep the window in front. I suspect this could be causing the problem. However, given the eradic nature of the bug I cannot confirm. I chose to replace the pop up window with an in-window div so I will not likely be investigating this bug further. I was able to reproduce the bug in v1.5.12 however it happens less often. A co-worker was able to reproduce it on Win XP Pro 32-bit with v2.0.22 and a client on Mac OS X encountered the bug using v2.0.22

Comment 3

[Tyler Downer [He/Him]]

This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode

Comment 4

[Tyler Downer [He/Him]]

No reply, INCOMPLETE. Please retest with Firefox 3.6.x 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.