488113 - "running but not responding" should not appear while the previous instance updates extensions

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Pascal Germroth]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.7) Gecko/2009030422 Ubuntu/8.10 (intrepid) Firefox/3.0.7
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.9.0.7) Gecko/2009030422 Ubuntu/8.10 (intrepid) Firefox/3.0.7

Firefox behaves user-unfriendly regarding second instances, while updating its extensions. (For example, first instance updates, second instance launched by clicking a link in Thunderbird. Currently, the second instance warns about a not-responding first instance, making the user think it crashed. They have to wait until updating completed, then click the link again.)

Reproducible: Always

Steps to Reproduce:
1. Launch firefox with outdated extensions, you see the update window
2. Launch another firefox with an URL
Actual Results:  
The second instance it will tell you a previous instance is running but not responding.

Expected Results:  
The first instance, that's currently updating should respond to the second instance, save their URL to the session, continue update, and after restarting open the saved session, including the URL the second instance wanted to open.


This new behaviour should be announced somehow: show an information bar "Page %s will be shown after updating is completed", set WM alert state for the window.

Comment 1

[Tyler Downer [He/Him]]

This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.

Comment 2

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 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.