If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Keep Crashing on opening after installing a plug in!

RESOLVED EXPIRED

Status

()

Firefox
General
--
critical
RESOLVED EXPIRED
13 years ago
12 years ago

People

(Reporter: Troy, Assigned: Blake Ross)

Tracking

({crash})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.5.6 (KHTML, like Gecko) Safari/125.12
Build Identifier: Firefox 1.0.1

I was on cartogra.com, a HP site that allows me to make personalized greeting card.  Once I was ready 
to print the card, it requested me to install a plug in manually.  Then, I downloaded the plug in and 
installed it.  During the installation, my Firefox browser quit unexpectedly.  Eventhough the plug in 
installed succesfully, I am unable to open firefox ever since.  Everytime when I open it, it just quit and 
crash reporter pops up.  This is still happening even after I reinstalled, deleted old program and did a 
fresh installation.  I tried Disk Utility, etc but non is working, please help!

Reproducible: Always

Steps to Reproduce:
1. visit cartogra.com, make a greeting card and try to print it.  
2. It will ask you to install a plug in manually, once installed, it crashed the firefox
3. Reopen the browser, and it would crash while opening
Actual Results:  
I can never open Firefox again, everytime I do, it crashed at the beginning

Expected Results:  
Should have not crashed on start

Comment 1

13 years ago
Could this be an error in the plugin ? Reporter, please attach one of those
crash dump as an attachement (not inline). You can get the file from the Console
appliction (in Utilities). The file contains multiple crash-dumps, so you might
want to take a copy first, then edit the file until there's only 1 left.

Updated

13 years ago
Keywords: crash
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.