248184 - Freeze after installing two specific extensions in one session; "Finishing Installing Extensions" forever

Status: RESOLVED DUPLICATE of bug 247322

(Toolkit :: Add-ons Manager, defect)

Description

[M. Creidieki Crouch]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040620
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040617 Firefox/0.9

I recently decided to install some Firefox extensions, and Firefox refused to
start afterwards.  I narrowed down the list to two extensions which, if
installed  in the same browser session, will disable Firefox.

Reproducible: Always
Steps to Reproduce:
1. Close Firefox, if open.
2. Delete ~/.mozilla to clear the profile.
3. Start Firefox; do not import a profile.
4. Click Tools->Extensions, then click "Get More Extensions"
5. Install ReloadEvery 0.3.
6. Without restarting Firefox, install UndoCloseTab 20040525.
7. Close Firefox.
8. Attempt to open Mozilla Firefox.

Actual Results:  
A window titled "Finishing Extension Installation..." popped up, which informed
me "Firefox is finishing installing extensions. This could take a minute..." . 
This window never went away.

Expected Results:  
Firefox should have started.

This may be related to Bug 246687 (which relates to installing different
versions of the same extension) or Bug 248013 (which relates to installing the
same extension twice without restarting).

This may be a duplicate of one of the issues in Bug 246658; I filed a new bug
because that bug covers several issues and does not include a test case.

WORKAROUND: If you suffer from this bug, deleting
~/.mozilla/firefox/{profile}/extensions is sufficient to fix your installation;
the entire profile does not need to be deleted.

Comment 1

[PikeUK]

This is because the maxVersion of UndoCloseTab (the one listed at
update.mozilla.org anyway) is 0.8.0+, so installing the extension will trigger
Bug 247322.

You can get the correct Firefox 0.9 compatible version here:

http://mozilla.dorando.at/readme.html

*** This bug has been marked as a duplicate of 247322 ***