Closed
Bug 123358
Opened 23 years ago
Closed 22 years ago
Crash on quit [@ CarbonCallBackSetup]
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: masri, Assigned: asa)
Details
(Keywords: crash)
Crash Data
I quit Fizzilla, then, while waiting for it to finish closing its windows and quit, I clicked into another open application, and quit that application (TextEdit). When that app quit, Fizzilla regained focus. The rainbow cursor continued to spin for a bit, then it crashed. Here's a stack trace. Date/Time: 2002-02-03 18:57:06 -0800 OS Version: 10.1.2 (Build 5P48) Host: localhost Command: Mozilla PID: 558 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x77696e64 Thread 0: #0 0x7003f4c8 in semaphore_wait_signal_trap #1 0x7003f2c8 in _pthread_cond_wait #2 0x70560b84 in DisableEventProcessing #3 0x7055be84 in CloseOpenTransportPriv #4 0x7055be44 in CloseOpenTransportInContext #5 0x004fe450 in CleanupTermProc #6 0x702c1d54 in TerminateConnection #7 0x70257c48 in ReleaseClosure #8 0x702c1c34 in TerminateApplication #9 0x702d2908 in ccAtExitRoutine #10 0x70005234 in exit #11 0x731039d8 in TThemeFont::ApplyStyleToContext(unsigned long, CGContext *) #12 0x00513ad8 in _exit #13 0x00513a34 in exit Thread 1: #0 0x7000497c in syscall #1 0x70557600 in BSD_waitevent #2 0x70554b80 in CarbonSelectThreadFunc #3 0x7002054c in _pthread_body Thread 2 Crashed: #0 0x77696e64 in 0x77696e64 #1 0x70553850 in CarbonCallBackSetup #2 0x70551118 in ProcessEventQueue #3 0x70552fd4 in CarbonDispatchThread #4 0x705581bc in AsyncInetStringToAddress #5 0x705594d4 in CarbonOperationThreadFunc #6 0x7002054c in _pthread_body Thread 3: #0 0x7003f4c8 in semaphore_wait_signal_trap #1 0x7003f2c8 in _pthread_cond_wait #2 0x70250ab0 in TSWaitOnCondition #3 0x7027d730 in TSWaitOnSemaphoreCommon #4 0x702c2078 in TimerThread #5 0x7002054c in _pthread_body Thread 4: #0 0x7003f4c8 in semaphore_wait_signal_trap #1 0x7003f2c8 in _pthread_cond_wait #2 0x70250ab0 in TSWaitOnCondition #3 0x7027d730 in TSWaitOnSemaphoreCommon #4 0x70243d14 in AsyncFileThread #5 0x7002054c in _pthread_body Thread 5: #0 0x7003f4c8 in semaphore_wait_signal_trap #1 0x7003f2c8 in _pthread_cond_wait #2 0x7055b884 in CarbonInetOperThreadFunc #3 0x7002054c in _pthread_body Thread 6: #0 0x70000978 in mach_msg_overwrite_trap #1 0x70005a04 in mach_msg #2 0x70026a2c in _pthread_become_available #3 0x70026724 in pthread_exit #4 0x70020550 in _pthread_body PPC Thread State: srr0: 0x77696e64 srr1: 0x4000f030 vrsave: 0x00000000 xer: 0x00000018 lr: 0x7055386c ctr: 0x77696e64 mq: 0x00000000 r0: 0x70553850 r1: 0x016aeb40 r2: 0x016aabac r3: 0x000003f3 r4: 0x10000001 r5: 0xfffff39e r6: 0x03173528 r7: 0x01000000 r8: 0x02d03cb8 r9: 0x000003ea r10: 0x000461a0 r11: 0x80550300 r12: 0x77696e64 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000 r16: 0x00000000 r17: 0x00000000 r18: 0x00000001 r19: 0x00000000 r20: 0x80550068 r21: 0x00000001 r22: 0x03173528 r23: 0xfffff39e r24: 0x034561b8 r25: 0x03173528 r26: 0x10000001 r27: 0xfffff39e r28: 0x77696e64 r29: 0x02d03af4 r30: 0x02d03ae0 r31: 0x70553814 **********
Reporter | ||
Comment 1•23 years ago
|
||
Platform: PowerBook G3/300/192Mb/48Gb, MacOS X 10.1.2 Fizzilla build: 2002013008 Oops, sorry, forgot to list my system specs. - Adam
Keywords: crash
QA Contact: doronr → zach
Summary: Crash on quit → Crash on quit [@CarbonCallBackSetup]
Comment 2•23 years ago
|
||
is this the mach-o build or the standard CFM one? qa back to default until we know it is mach-o
QA Contact: zach → doronr
Reporter | ||
Comment 3•23 years ago
|
||
I'm not running mach-o builds. - Adam
Assignee | ||
Comment 4•22 years ago
|
||
Adam, are you seeing this with the latest 0S X builds and a new profile?
Reporter | ||
Comment 5•22 years ago
|
||
Platform: PowerBook G3/300/192Mb/48Gb, MacOS X 10.1.3 Fizzilla Build: 2002022613 No. I just tried it, using SimpleText as the second app. Moz quit and did not crash. Whether the bug that caused this crash is fixed or not, I don't know. - Adam
Could this be moved to XP Apps or XP Miscellany instead of Browser-General?
Summary: Crash on quit [@CarbonCallBackSetup] → Crash on quit [@ CarbonCallBackSetup]
um, afaik none of that crash is in mozilla code. which is really really problematic.
Assignee: asa → new-network-bugs
Component: Browser-General → Networking
QA Contact: doron → benc
Adam, as the reporter, if you don't see this post 1.0, can you mark RESOLVED/WFM? I don't see problems like this, I work on Mac OS X (mozilla 1.0 and chimera 0.3) 80% of the day now.
-> browser general - don't know why this is networking...
Component: Networking → Browser-General
Comment 11•22 years ago
|
||
Resolving as WFM due to comment 5
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•13 years ago
|
Crash Signature: [@ CarbonCallBackSetup]
You need to log in
before you can comment on or make changes to this bug.
Description
•