Closed Bug 310489 Opened 19 years ago Closed 19 years ago

crash if a incompatible extension is installed when launching Firefox (crash only the first time,)

Categories

(Toolkit :: Add-ons Manager, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: frenchfrog, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20050929 Firefox/1.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20050929 Firefox/1.4

Check the steps below:

Reproducible: Always

Steps to Reproduce:
1.Install easyGesture 3.1
(https://addons.mozilla.org/extensions/moreinfo.php?id=29) in Firefox 1.0+ (Deer
Park before Firefox 1.5 Beta)
2.Restart Firefox 1.0+ so easyGesture 3.1 finish is installation
3.Start Firefox 1.8 Branch (Firefox 1.5 Beta)
4.A dialog will popup to tell you that easyGesture 3.1 is not compatible
5.Click "Check now" button or the don't check for update button


Actual Results:  
Firefox crash without talkback, if you start Firefox a second time it won't
crash and easyGesture 3.1 will be disabled (which is the correct behaviour).
I'm not positive but from reading the report it appears you found this with Deer
Park and not beta 1 yet you are running a  recent nightly. Can you reproduce
with a recent nightly?
dupe of 307235?
Comment #1: from the report: User-Agent:       Mozilla/5.0 (Windows; U; Windows
NT 5.1; en-US; rv:1.8b5) Gecko/20050929 Firefox/1.4

Comment #2: it crash, not hang
I am quite sure this was fixed by the patch that landed just after beta 1 in bug
307569... it at times also caused a crash.

*** This bug has been marked as a duplicate of 307569 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Ok, let me exlain this in more details (sorry for the confusion)

The firefox that is crashing is: 20050929 Firefox/1.4

The reason I install easyGesture 3.1 in Firefox 1.0+ (Deer
Park before Firefox 1.5 Beta) it's because it's only compatible with 1.0+ not
with 1.0.x, 1.4 or 1.6a1
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Ok here a easier way to crash Firefox 1.8 branch (Firefox 1.5 beta), almost the
same as comment #0 but with StumbleUpon 2.03 which is easier to install since it
could be install in 1.0.x contrary to easyGesture 3.1

1.Install StumbleUpon 2.03 in Firefox 1.0.x
(http://mirrors.xmission.com/mozilla.org/extensions/stumbleupon/stumbleupon-2.02-fx+mz+ns.xpi)
which is not compatible with 1.4 
2.Restart Firefox 1.0.x
3.Start Firefox 1.8 Branch (Firefox 1.5 Beta)
4.A dialog will popup to tell you that StumbleUpon 2.03 is not compatible
5.Click the don't check for update button

Actual Results:  
Firefox crash without talkback, if you start Firefox a second time it won't
crash and StumbleUpon 2.03 will be disabled (which is the correct behaviour).
On both Win32 and Linux I performed the following several times:
installed DPA2
launched with a new profile.
installed stumbleupon
restarted, verified it installed, exited
installed the 20050929 nightly
restarted and clicked the check now / don't check button during the
incompatibility check

I am unable to reproduce.
Also of note, you were able to reproduce this with beta 1 per comment #0. After
beta 1 there was QA testing specifically for the wizard in bug 307571 and there
were no reports of a crash when clicking either of those buttons in the wizard.
I suspect this will be very difficult for others to reproduce / track down.
Ok, I done more testing,

I uninstalled the 3 versions of Firefox I had on my box (1.0.7, 1.6a1, 1.4)
deleted the directories of each of them, reinstalled them.

And now it doesn't crash!

It means that there was something in one of the directories that made Firefox
1.4 (Firefox 1.5 Beta 1) crash. (because only reinstalling the 3 firefox over
the existing directories still crashed Firefox)

Problem is, I don't have the old directories anymore to test why it did crash :/

(The only possible cause I coud think is that some extensions were perhaps
installed twice, one in the profile and one the application folder)

I'll verify this avenue and report back if successful.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → WORKSFORME
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.