Closed Bug 43163 Opened 25 years ago Closed 22 years ago

crash on startup when QUIT AppleEvent sent

Categories

(SeaMonkey :: General, defect, P4)

PowerPC
Mac System 8.6
defect

Tracking

(Not tracked)

RESOLVED WONTFIX
Future

People

(Reporter: qaz2, Assigned: sfraser_bugs)

Details

(Keywords: crash, Whiteboard: [nsbeta3-][p:4][Mac issue])

From Bugzilla Helper: User-Agent: Mozilla/4.06 (Macintosh; I; PPC, Nav) BuildID: 2000061411 It is possible, while Mozilla is loading, to switch to another application. If I send a QUIT AppleEvent from a program such as Memory Mapper or from a control strip module, Mozilla will crash. Reproducible: Always Steps to Reproduce: 1.Open Mozilla. 2.When you can, switch to a program capable of sending QUIT AppleEvents, and send one to Mozilla. Actual Results: Mozilla crashes. Expected Results: Mozilla should have quit. how: PowerPC access exception at 05D4DFFC NSGetModule+2C13C sc: Calling chain using A6/R1 links Back chain ISA Caller 00000000 PPC 06082F7C 070A1A00 PPC 06073DF4 070A19A0 PPC 05F3FAF4 NS_ShutdownXPCOM(nsIServiceManager*)+00140 070A1890 PPC 05F09F08 nsServiceManager::ShutdownGlobalServiceManager(nsIServiceManager **)+00028 070A1840 PPC 05F09448 nsGetServiceByProgID::~nsGetServiceByProgID()+00534 070A1800 PPC 05F093A4 nsGetServiceByProgID::~nsGetServiceByProgID()+00490 070A17C0 PPC 05F047B0 nsObjectHashtable::~nsObjectHashtable()+00020 070A1780 PPC 05F048F4 nsObjectHashtable::Reset()+00014 070A1740 PPC 05F04430 nsHashtable::Reset(int (*)(nsHashKey*, void*, void* ), void*)+000 2C 070A1700 PPC 0600AAD8 PL_HashTableEnumerateEntries+00060 070A1690 PPC 05F043A4 nsHashtable::Enumerate(int (*)(nsHashKey*, void*, void*), void*) +00060 070A1650 PPC 05F09294 nsGetServiceByProgID::~nsGetServiceByProgID()+00380 070A1610 PPC 05DD199C NSGetModule+00694 070A15D0 PPC 05DD1834 NSGetModule+0052C 070A1560 PPC 05DCA418 070A1520 PPC 05DCCD00 070A1470 PPC 05DE0EB0 NS_NewScriptXPConnectFactory+0A8A4 070A1370 PPC 05F8A50C nsGetInterface::nsGetInterface(nsISupports*, unsigned int*)+03A0 4 070A1320 PPC 05F960D8 NS_NewWebShellFactory+09ED4 070A12C0 PPC 05F839D4 NS_TotalWebShellsInExistence+00754 070A1280 PPC 05F0B8AC nsCOMPtr_base::assign_with_AddRef(nsISupports*)+ 00048 070A1240 PPC 059FD724 nsStyleChangeList::Clear()+1067C 070A1200 PPC 059FDBB4 nsStyleChangeList::Clear()+10B0C 070A1160 PPC 05CE79B0
Sounds like a real bug.
Assignee: asa → sfraser
Status: UNCONFIRMED → NEW
Ever confirmed: true
what component would this be?
Adding crash keyword
Keywords: crash
setting to m17
Severity: minor → critical
Priority: P3 → P1
Target Milestone: --- → M17
Need to fix this in M18
Status: NEW → ASSIGNED
Keywords: correctness, nsbeta3
Target Milestone: M17 → M18
setting to nsbeta3+
Whiteboard: nsbeta3+
setting priority in status whiteboard-low risk but may take alot of time
Priority: P1 → P4
Whiteboard: nsbeta3+ → [nsbeta3+][p:4]
update whiteboard
Whiteboard: [nsbeta3+][p:4] → [nsbeta3+][p:4][Mac issue]
moving to m19, higher priority bugs need to be addressed for b3
Whiteboard: [nsbeta3+][p:4][Mac issue] → [nsbeta3-][p:4][Mac issue]
Target Milestone: M18 → M19
moving out to future
Target Milestone: M19 → Future
Severity: critical → normal
removing myself from the cc list
I run into a similar error when starting Mozilla 1.2, but not 1.1. I have switched back to the 1.1 to avoid this problem. Additionally, the force quit option does not always quit the program, and you are stuck with unplugging the machine. This problem seems to be related to the Netscape Problem Report form that starts up after a forced quit. That seems to be what triggers the freeze in 1.2.
By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and <http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss bugs are of critical or possibly higher severity. Only changing open bugs to minimize unnecessary spam. Keywords to trigger this would be crash, topcrash, topcrash+, zt4newcrash, dataloss.
Severity: normal → critical
qaz2@usa.netqaz2@usa.net, can you still reproduce this using a FizzillaMach build on Mac OS X? (Mac OS 9 and earlier are no longer supported.)
I have never seen this on Mac OS X (with any application), so I guess it's a works-for-me.
mac classic only, marking WONTFIXm because mac classic is no longer supported. Please reopen if you see this on other operating systems as well.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.