Closed Bug 791149 Opened 12 years ago Closed 7 years ago

startup crash in [@ nsParseMailMessageState::FinalizeHeaders()]

Categories

(MailNews Core :: Backend, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: wsmwk, Unassigned)

References

Details

(Keywords: crash, Whiteboard: [startupcrash])

Crash Data

This bug was filed from the Socorro interface and is report bp-c5fceb39-3e48-45e3-ac3c-d5a862120813 . ============================================================= Frame Module Signature Source 0 msvcr80.dll strlen F:\dd\vctools\crt_bld\SELF_X86\crt\src\intel\strlen.asm:69 1 xul.dll nsParseMailMessageState::FinalizeHeaders mailnews/local/src/nsParseMailbox.cpp:1346 2 xul.dll nsParseMailMessageState::ParseFolderLine mailnews/local/src/nsParseMailbox.cpp:711 3 xul.dll nsMsgMailboxParser::HandleLine mailnews/local/src/nsParseMailbox.cpp:526 4 xul.dll nsPop3Sink::WriteLineToMailbox mailnews/local/src/nsPop3Sink.cpp:750 5 xul.dll nsPop3Sink::IncorporateWrite mailnews/local/src/nsPop3Sink.cpp:737 6 xul.dll nsPop3Protocol::HandleLine mailnews/local/src/nsPop3Protocol.cpp:3636 7 xul.dll nsPop3Protocol::RetrResponse mailnews/local/src/nsPop3Protocol.cpp:3396 8 xul.dll nsPop3Protocol::ProcessProtocolState mailnews/local/src/nsPop3Protocol.cpp:4021 9 xul.dll nsMsgProtocol::OnDataAvailable mailnews/base/util/nsMsgProtocol.cpp:389 10 xul.dll nsInputStreamPump::OnStateTransfer netwerk/base/src/nsInputStreamPump.cpp:518
Another couple of functions returning int instead of nsresult... But I can't see the reason for the crash. Is this a single occurrence of this signature?
OS: Windows NT → Windows XP
Version: unspecified → 14
(partly in followup to bug 877831 comment 14) Hiro had a patch in Bug #877831, fixed in TB 24.0.1 or 24.0.2? ... bug we still have this startup crashes: bp-94460041-e6e6-425f-b6cd-d98842140723 TB31.0 bp-0723a2fb-0ba4-4b39-a641-5ed772140801 TB31.0 linux bp-d1a459b6-20c5-48b2-ab42-8dc152140717 TB24.6.0 bp-b8832e62-f6a3-409d-aefe-9ecc52140805 TB24.6.0 Non-startup crashes are covered in bug 1051616 - but I don't know for a fact that any of them are different than the crashes cited in this bug. hiro do you want to continue your great work here?
Crash Signature: [@ strlen | nsParseMailMessageState::FinalizeHeaders()] → [@ strlen | nsParseMailMessageState::FinalizeHeaders()] [@ nsParseMailMessageState::FinalizeHeaders()] [@ nsParseMailMessageState::FinalizeHeaders]
Flags: needinfo?(hiikezoe)
Summary: crash in [@ nsParseMailMessageState::FinalizeHeaders()] → startup crash in [@ nsParseMailMessageState::FinalizeHeaders()]
Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.
Crash Signature: [@ strlen | nsParseMailMessageState::FinalizeHeaders()] [@ nsParseMailMessageState::FinalizeHeaders()] [@ nsParseMailMessageState::FinalizeHeaders] → [@ strlen | nsParseMailMessageState::FinalizeHeaders()] [@ nsParseMailMessageState::FinalizeHeaders()] [@ nsParseMailMessageState::FinalizeHeaders] [@ strlen | nsParseMailMessageState::FinalizeHeaders]
(In reply to :aceman from comment #1) > Another couple of functions returning int instead of nsresult... > > But I can't see the reason for the crash. Is this a single occurrence of > this signature? see bug 1051616
Flags: needinfo?(hiikezoe)
no crashes for >2 months strlen | nsParseMailMessageState::FinalizeHeaders only 6 crashes for nsParseMailMessageState::FinalizeHeaders, all 52.5.2. I think only bp-e24ad70e-d067-4e68-bf20-57b200180108 has s decent stack. None are startup, so they are all of the flavor of bug 1051616. No crashes since Feb 1, and no crashes in 52.6.0.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.