User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030307 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030307 When the most recent calendar (February 14th 2003) is installed, Mozilla will crash at the next startup. Removing all calendar related components from the install folder stops Mozilla from crashing :) Reproducible: Always Steps to Reproduce: 1. Install Calendar 2. Close Mozilla 3. Start Mozilla Actual Results: *CRASH* Expected Results: It should have started normally Talkback crash IDs: TB17888785X TB17888771X
I can confirm this issue in 2003030717 on Windows XP Home SP1, but it is not Calendar specific since this is happening with any XPI install package. It may be related to bug 194030, but I am sure it is not a duplicate of it. Talkback does not capture the crashes that I get. However, the error message I get says the crash is in xpcom.dll if I remember correctly.
Status: UNCONFIRMED → NEW
Component: Calendar General → Installer: XPInstall Engine
Ever confirmed: true
Product: Calendar → Browser
Summary: Calendar crashes Mozilla → restart after XPI install causes crash
Version: unspecified → Trunk
That's strange, on my system mozilla.exe crashes
This is a dupe of 195614 http://bugzilla.mozilla.org/show_bug.cgi?id=195614 . This one depends on 134432 Polease check if it is not a dupe of 194030 too
Not a blocker.
Severity: blocker → critical
do you still crash with 1.4 or 1.5a ?
New contact from email@example.com to firstname.lastname@example.org Filter on string OttawaMBA to get rid of these messages. Sorry for the spam.
Assignee: mikep → mostafah
Zarco Zwier: Can you still reproduce this crash with 1.7b or newer build? Could you provide new TalkBack incident ID?
Not able to reproduce or not able provide TB ID or "no" for both questions?
Not reproducable, so I can't provide a TB ;)
So I'm marking this bug as WFM. Thanx for testing and bug-reporting.
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.