Closed Bug 483961 Opened 15 years ago Closed 15 years ago

crash [@ nsImapOfflineSync::ProcessNextOperation()]

Categories

(MailNews Core :: Networking: IMAP, defect)

Product:
MailNews Core
Component:
Networking: IMAP
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: wsmwk, Assigned: Bienvenu)

Details

(Keywords: crash, topcrash)

Crash Data

This is a Eudora topcrash 
3.0b1pre

xref old bug 285791

bp-89c597a9-6667-4c83-a6ea-6ced52090317
0  	eudora.exe  	nsImapOfflineSync::ProcessNextOperation  	nsImapOfflineSync.cpp:831
1 	eudora.exe 	nsImapMailFolder::UpdateFolder 	nsImapMailFolder.cpp:757
2 	eudora.exe 	nsImapMailFolder::InitiateAutoSync 	nsImapMailFolder.cpp:8465
3 	eudora.exe 	nsAutoSyncManager::TimerCallback 	nsAutoSyncManager.cpp:289
4 	xpcom_core.dll 	nsTimerImpl::Fire 	xpcom/threads/nsTimerImpl.cpp:420
5 	xpcom_core.dll 	nsTimerEvent::Run 	xpcom/threads/nsTimerImpl.cpp:512
6 	xpcom_core.dll 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:510
7 	xpcom_core.dll 	NS_ProcessNextEvent_P 	nsThreadUtils.cpp:227
8 	eudora.exe 	nsBaseAppShell::Run 	widget/src/xpwidgets/nsBaseAppShell.cpp:170
9 	eudora.exe 	nsAppStartup::Run 	toolkit/components/startup/src/nsAppStartup.cpp:19
I'll be interested to know if this still happens after the fix for bug 480090, which landed today.
Assignee: nobody → bienvenu
(In reply to comment #1)
> I'll be interested to know if this still happens after the fix for bug 480090,
> which landed today.

bienvenu, jeff, it turns out this crash *only* existed in build 20090108100404 3.0b1pre.  I can't tell from crash stats what date build the crashes ended on prior to ~1/1/2009 -- based on crash stats it seems they started on 2009-03-16 00:00
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Summary: crash [@ nsImapOfflineSync::ProcessNextOperation] → crash [@ nsImapOfflineSync::ProcessNextOperation()]
Crash Signature: [@ nsImapOfflineSync::ProcessNextOperation()]
You need to log in before you can comment on or make changes to this bug.