492886 - Add-on installation restart hangs and clears tabs.

Status: RESOLVED WONTFIX

(Toolkit :: Add-ons Manager, defect)

Description

[patrickjdempsey]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1b4) Gecko/20090423 Firefox/3.5b4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1b4) Gecko/20090423 Firefox/3.5b4

If the Privacy setting "Clear history when Firefox closes" is selected, the browser will not reload tabs on an add-on installation restart.  It also causes the browser to "hang" which can be fixed by starting another session of Firefox.

If "Never remember history" is selected, the browser restarts fine with the correct tabs loaded.

Reproducible: Always

Steps to Reproduce:
1. Check "Clear history when Firefox closes" under Privacy.
2. Open multiple tabs.
3. Install add-on or change theme.
4. Select "Restart"
Actual Results:  
Browser hangs after shutting down and will not restart.  When a new session is manually started, the new session appears along with the restarted session, except that the tabs have been cleared.

Expected Results:  
The browser should automatically restart by itself with the same tabs open as in the previous session, no matter what the Privacy settings are.  This is the expected behavior from previous versions.  

Since restarting the browser after installing an Add-on or changing a Theme is not a Privacy issue, it should not follow this Privacy rule.  It is not uncommon for people to change themes or update Add-ons while browsing and they except the browser to restart with the tabs they have selected.  I do not see a "Session restore" dialog when I restart in this scenario.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+2]]

I saw this twice today on Windows XP and OS X. The first time I thought the process went somehow crazy. But a couple of minutes ago I had the same situation on OS X while running the BFT.

With the steps in comment 0 it is not always reproducible. I went back with time machine and tried to do the same steps as I did before but without success for now. So what I have seen was that all windows are getting closed but the process was still running. A new window could be opened by clicking the icon in the dock. I did a shark profile but I don't guarantee for its correctness because it isn't a shark enabled build. I will attach it right now.

No idea how we should handle this. Since we don't have reliable steps or a hang analysis we can't do anything. I will further have a look at this bug while continue testing.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Attachment: Shark profile

Comment 3

[Andy McKay]

Due to a long period of inactivity on this bug (5.04 years), I am intending to close this bug within a month or so in accordance with: https://wiki.mozilla.org/Add-ons/OldBugs Please remove [intent-to-close] from the whiteboard and comment on this bug if you would like to keep it open.