Closed
Bug 97523
Opened 24 years ago
Closed 24 years ago
Mac: crash on quit after changing mail pref
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: bugzilla, Assigned: bugzilla)
Details
(Keywords: crash)
Attachments
(1 file)
seen this using 2001.08.29.0x-comm bits on Mac OS X and OS 9.1; have
yet to see it on win32 or linux.
warning: the problem here is reproducibility. :( i cannot seem to get this to
happen all the time [will provide a recipe as well as stack info below]. but
it has happened several times, so thought it couldn't hurt to file... anyhow,
any suggestions on narrowing down a better/simpler test case are
welcomed!
0. make sure you have a mail acct already setup. the one i have is the
3qatest01 one using imap.
1. start up the browser, and bring up the prefs dialog.
2. make a change --eg, i deselect some of the toolbar items in the
Navigator panel-- then click OK to save/dismiss prefs.
3. bring up mail, eg, select Tasks > Mail & news.
4. open up prefs again: it should be at the toplevel Mail and Newsgroups
panel.
5. change the General Settings section, change the mailnews window
layout selection.
6. click OK to save/dismiss prefs.
7. quit the app entirely --eg, i hit cmd+Q.
result: crash on quitting. [however, the next time i restart, the changes i've
made in prefs are in effect.]
sometimes i don't even need to modify a navigator pref beforehand --it'll
crash on quit after only modifying the mailnews pref. however, sometimes
i can go through the above recipe several times without a crash occurring.
hrm. :-/
anyhow, here are the stacks:
Mac OS X
-------------
Date/Time: 2001-08-29 11:52:07 -0700
PID: 393
Command: Netscape 6
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
Thread 0:
#0 0x00000000 in 0x0 ()
#1 0x04811308 in
RemoveConnection__20nsImapIncomingServerFP15nsIImapProtocol ()
#2 0x0483f19c in Run__14nsImapProtocolFv ()
#3 0x00181b1c in Main__8nsThreadFPv ()
#4 0x000d4d90 in 0xd4d90 ()
Thread 1:
#0 0x7000424c in _syscall ()
#1 0x706584b8 in _ProcessReadyEvent ()
#2 0x706582b0 in _CarbonSelectThreadFunc ()
#3 0x70014f04 in __pthread_body ()
Thread 2:
#0 0x70059b68 in _semaphore_wait_signal_trap ()
#1 0x70016110 in _semaphore_wait_signal ()
#2 0x70015f78 in __pthread_cond_wait ()
#3 0x70015d18 in _pthread_cond_wait ()
#4 0x70653be0 in _BSD_pthread_cond_wait ()
#5 0x70653bc0 in _CarbonConditionWait ()
#6 0x7065557c in _CarbonOperationThreadFunc ()
#7 0x70014f04 in __pthread_body ()
Thread 3:
#0 0x70059b48 in _semaphore_timedwait_signal_trap ()
#1 0x7003f7f8 in _semaphore_timedwait_signal ()
#2 0x70015f68 in __pthread_cond_wait ()
#3 0x7003f7c4 in _pthread_cond_timedwait_relative_np ()
#4 0x7029b590 in _TSWaitOnConditionTimedRelative ()
#5 0x7029cdac in _TSWaitOnSemaphoreCommon ()
#6 0x702e5f98 in _TSWaitOnSemaphoreRelative ()
#7 0x702e7208 in _TimerThread ()
#8 0x70014f04 in __pthread_body ()
Thread 4:
#0 0x70059b68 in _semaphore_wait_signal_trap ()
#1 0x70016110 in _semaphore_wait_signal ()
#2 0x70015f78 in __pthread_cond_wait ()
#3 0x70015d18 in _pthread_cond_wait ()
#4 0x7029b550 in _TSWaitOnCondition ()
#5 0x7029cd94 in _TSWaitOnSemaphoreCommon ()
#6 0x7029cce4 in _TSWaitOnSemaphore ()
#7 0x7029cba8 in _AsyncFileThread ()
#8 0x70014f04 in __pthread_body ()
Thread 5:
#0 0x70059b68 in _semaphore_wait_signal_trap ()
#1 0x70016110 in _semaphore_wait_signal ()
#2 0x70015f78 in __pthread_cond_wait ()
#3 0x70015d18 in _pthread_cond_wait ()
#4 0x70653be0 in _BSD_pthread_cond_wait ()
#5 0x70653bc0 in _CarbonConditionWait ()
#6 0x70653ab4 in _CarbonInetOperThreadFunc ()
#7 0x70014f04 in __pthread_body ()
Thread 6:
#0 0x700007b8 in _mach_msg_overwrite_trap ()
#1 0x700056e4 in _mach_msg_overwrite ()
#2 0x700277b0 in _thread_suspend ()
#3 0x70027744 in __pthread_become_available ()
#4 0x70027468 in _pthread_exit ()
#5 0x70014f08 in __pthread_body ()
PPC Thread State:
srr0: 0x00000000 srr1: 0x4000f030 vrsave: 0x00000000
xer: 0x2000000c lr: 0x04811328 ctr: 0x00000000 mq: 0x00000000
r0: 0x00000000 r1: 0x02c2bbf0 r2: 0x00000000 r3: 0x04745f60
r4: 0x03e0b3f0 r5: 0x000d970c r6: 0x28000008 r7: 0x02d97c44
r8: 0x01d138bc r9: 0x01d126b4 r10: 0x01d126c4 r11: 0x00000001
r12: 0x003a0061 r13: 0x00000000 r14: 0x00000000 r15: 0x048d3150
r16: 0x002c8738 r17: 0x002c66a8 r18: 0x002c874c r19: 0x002c8740
r20: 0x02c2be40 r21: 0x002c8700 r22: 0x002c8754 r23: 0x002c872c
r24: 0x002c3d50 r25: 0x03e0b45c r26: 0x000e3a39 r27: 0x002c8698
r28: 0x002c86c8 r29: 0x00000000 r30: 0x04746e40 r31: 0x03e0b3f0
Mac 9.1 [classic emulation over X]
----------------------------------------------
Talkback #34686902
Stack Signature 0xffc10004 198648cb
Trigger Time 2001-08-29 12:17:37
User Comments crash on quit after changing mailnew window layout
pref
Build ID 2001082908
Product ID MozillaTrunk
Platform ID MacOS
Trigger Reason Illegal PowerPC instruction
Stack Trace 0xffc10004
nsImapProtocol::Run() [nsImapProtocol.cpp, line 752]
nsThread::Main() [nsThread.cpp, line 105]
_PR_UserRunThread() [pruthr.c, line 503]
_PR_UserDestroyThread() [pruthr.c, line 374]
| Reporter | ||
Comment 1•24 years ago
|
||
pink --i know the crash on quit you had seen had a different stack, but
thought i'd cc you here since this involved changing a pref on mac...
Keywords: crash
I've just followed above scenarios - can not reproduce the crash on Mac OSX.
| Assignee | ||
Comment 6•24 years ago
|
||
accepting...
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0
Comment 7•24 years ago
|
||
Anyone seeing this lately or does anyone thing this could be 99561 as Simon
mentioned?
Keywords: nsbeta1
Target Milestone: mozilla1.0 → ---
Comment 8•24 years ago
|
||
This looks like the old 'crash on quit after using IMAP' bug, which was fixed no?
Comment 10•24 years ago
|
||
Discussed in 2/26 bug meeting with Mktg Engineering and PjM. Decision was to
resolve worksforme.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
I haven't seen this, either. 2002-03-14-08, OS X 10.1.3.
Verified.
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•