663275 - leaving a dialog (Save as, Attach file) open triggers an unresponsive script dialog

Status: RESOLVED WORKSFORME

(Core :: Widget, defect)

Description

[Ben Milman]

User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0.1) Gecko/20100101 Firefox/4.0.1

in firefox or thunderbird, leaving a dialog open for a few minutes without touching it will trigger the "unresponsive script" dialog. When that appears, the dialog left open will be disabled but not removed (ie, cancel or print buttons are disabled, but the box is still there). Because the initial dialog is disabled, it is impossible to dismiss the dialog. The "unresponsive script" dialog likewise cannot be dismissed, since the focus is held by the first, "unresponsive" dialog. The only escape from the lock is to hard-quit the program.

Reproducible: Always

Steps to Reproduce:
1.Open a print dialog in firefox, or an attach file dialog in thunderbird
2.leave open
3.unresponsive script dialog will appear, triggering the lock

Actual Results:  
browser is unusable (locked). Must restart browser to regain control.

Expected Results:  
either the "unresponsive" dialog is dismissed completely or user unresponsiveness is not treated as an unresponsive script

I know that this also works on PC-BSD 8.2, but I'm not sure what version of the browser that is, so I'm reporting it here. I believe this may be a duplicate ticket, but I could not find the original so I'm reporting it just in case.

Comment 1

[Tyler Downer [He/Him]]

What exactly is the unresponsive script, and do you get this in a fresh profile?

Comment 2

[Ben Milman]

In Firefox, it's the print dialog, and in Thunderbird, it's the attach file dialog. And yes, I do. The script is not unresponsive at all, it's just that the user doesn't respond to it for some time.

Comment 3

[Matthias Versen [:Matti]]

The hang is bug 476541 but a modal dialog should not trigger an unresponsive script warning

Comment 4

[Vlad [QA]]

I am also getting a freeze.
Comment 111 from bug 476541.

Comment 6

[Matthias Versen [:Matti]]

How is this a dupe of bug 476541 ?
bug 476541 is about a deadlock between the 2 dialogs.
This one here is that you get an unresponsive script dialog if you leave a dialog open and now you have bug 476541.

Comment 7

[Vlad [QA]]

If not a dupe, please change the status accordingly. 
Thx

Comment 8

[Wayne Mery (:wsmwk)]

Matti's point is why is there an unresponsive script during print dialog.

1. can you replicate this with something newer, like firefox 5, or a beta of version 6?

2. with *nothing* else running on the Mac, profile the cpu from just before doing print, to when you get "unresponsive"

Comment 9

[Vlad [QA]]

Reporter, is the issue still reproducible?
Please try on the latest Firefox beta:
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/releases/6.0b5/mac/en-US/

Comment 10

[Vlad [QA]]

Reporter, is this issue still reproducible?
Thanks

Comment 11

[Ben Milman]

I was unable to reproduce on Firefox 7.0.1 and Thunderbird 7.0.1. Thanks everyone!

Comment 12

[:aceman]

This does still exist on TB12.
For TB I got this in the attach file dialog:

A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.
Script: chrome://messenger/content/messengercompose/MsgComposeCommands.js:3961

Dismissing the script dialog and also attach dialog worked fine (no bug 476541 happening). This was on Win XP.

I couldn't reproduce on Firefox 12, but there is bug 714748 about it too.

Refined the summary to show this bug is only about the unresponsive script dialog. Bug 476541 is for the hang/lock (which may be Mac OS X specific).

Comment 14

[Till Schneidereit [:till]]

Could this be caused by or at least related to bug 384412?

In bug 714748, I described how I could only reproduce the problem by switching focus and how the script triggering the warning is in NetworkPrioritizer.jsm, which leads me to suspect that maybe Firefox lowers network priority on blur, which doesn't properly work if the interpreter is suspended because of a dialog.

Comment 16

[Negritas Sergiu, Desktop QA]

Hello I have tried to reproduce the issue with firefo 96.0a1(2021-11-29) with Ubuntu 20 and MacOS 10.15, unfortunately I couldn't reproduce the issue.

Marking this issue as RESOLVED->WORKSFORME since there is no activity in the past 10 years. If the issue is still valid please feel free to reopen it.

Thank you!