Closed Bug 31923 Opened 26 years ago Closed 25 years ago

assertions in nsMsgThread.cpp

Categories

(MailNews Core :: Backend, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME
Future

People

(Reporter: sspitzer, Assigned: Bienvenu)

Details

when messenger starts up, and selects my inbox, I get this assertion several times. NTDLL! 77f7629c() nsDebug::Assertion(const char * 0x02f6d348, const char * 0x02f6d32c, const char * 0x02f6d2f0, int 848) line 189 + 13 bytes nsMsgThread::ChangeChildCount(int -1) line 848 + 32 bytes nsMsgThread::RemoveChildHdr(nsMsgThread * const 0x03349e30, nsIMsgDBHdr * 0x033485e0, nsIDBChangeAnnouncer * 0x03031da0) line 439 nsMsgDatabase::RemoveHeaderFromDB(nsMsgHdr * 0x033485e0) line 1258 + 36 bytes nsMsgDatabase::DeleteHeader(nsMsgDatabase * const 0x03031da0, nsIMsgDBHdr * 0x033485e0, nsIDBChangeListener * 0x00000000, int 0, int 1) line 1218 + 18 bytes nsMsgDatabase::DeleteMessages(nsMsgDatabase * const 0x03031da0, nsMsgKeyArray * 0x0012fcdc, nsIDBChangeListener * 0x00000000) line 1168 + 43 bytes nsMailDatabase::DeleteMessages(nsMailDatabase * const 0x03031da0, nsMsgKeyArray * 0x0012fcdc, nsIDBChangeListener * 0x00000000) line 183 + 17 bytes nsImapMailFolder::UpdateImapMailboxInfo(nsImapMailFolder * const 0x01f6f730, nsIImapProtocol * 0x020d4028, nsIMailboxSpec * 0x03347690) line 1707 XPTC_InvokeByIndex(nsISupports * 0x01f6f730, unsigned int 10, unsigned int 2, nsXPTCVariant * 0x03341ac0) line 139 EventHandler(PLEvent * 0x03344030) line 481 + 41 bytes PL_HandleEvent(PLEvent * 0x03344030) line 563 + 10 bytes PL_ProcessPendingEvents(PLEventQueue * 0x00ff1be0) line 508 + 9 bytes _md_EventReceiverProc(HWND__ * 0x4c4b014e, unsigned int 49374, unsigned int 0, long 16718816) line 1018 + 9 bytes USER32! 77e71820() 00ff1be0()
If you delete your msf file, this will go away. I don't know how to get in this situation, so I don't know how to reproduce it.
accepting.
Status: NEW → ASSIGNED
Target M17.
Target Milestone: --- → M17
moving to future.
Target Milestone: M17 → Future
OK, I don't see this happen anymore - I suspect it's fixed. It might have had to do with some problem I fixed with thread counts.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
I don't see this either, on a current windows 2000 debug CVS pull.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.