Closed Bug 86428 Opened 23 years ago Closed 23 years ago

Crash in nsPop3Protocol::Commit [@ nsPop3Protocol::CommitState ]

Categories

(MailNews Core :: Networking: POP, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 83807

People

(Reporter: mscott, Assigned: naving)

Details

(Keywords: crash)

Crash Data

Got this from the talkback reports submitted by jbaltz@omnipod.com He's constantly crashing in ::CommitState on line 2519. This was seen for him using a build from June 7th. nsPop3Protocol::CommitState [d:\builds\seamonkey\mozilla\mailnews\local\src\nsPop3Protocol.cpp, line 2519] nsPop3Protocol::OnStopRequest [d:\builds\seamonkey\mozilla\mailnews\local\src\nsPop3Protocol.cpp, line 605] nsOnStopRequestEvent::HandleEvent [d:\builds\seamonkey\mozilla\netwerk\base\src\nsRequestObserverProxy.cpp, line 159] PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 591] PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 524] _md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 1072] nsAppShellService::Run [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsAppShellService.cpp, line 418] main1 [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1159] main [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1453] WinMain [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp, line 1471]
Keywords: crash, mozilla0.9.2
Summary: Crash in nsPop3Protocol::Commit → Crash in nsPop3Protocol::Commit [ @ nsPop3Protocol::CommitState ]
*** This bug has been marked as a duplicate of 83807 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified as dup
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
Severity: normal → critical
Summary: Crash in nsPop3Protocol::Commit [ @ nsPop3Protocol::CommitState ] → Crash in nsPop3Protocol::Commit [@ nsPop3Protocol::CommitState ]
Crash Signature: [@ nsPop3Protocol::CommitState ]
You need to log in before you can comment on or make changes to this bug.