Closed Bug 1051616 Opened 10 years ago Closed 4 years ago

crash nsParseMailMessageState::FinalizeHeaders due to wrong length of mozstatus

Categories

(MailNews Core :: Backend, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: wsmwk, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: crash)

Crash Data

+++ This bug was initially created as a clone of Bug #877831 +++ This bug is partly in followup to hiro's bug 877831 comment 14 ... despite hiro's patch in Bug #877831, fixed in TB 24.0.1 or 24.0.2? ... not startup: bp-2bd59dc5-7d61-4da8-8381-b99862140808 TB31.0 bp-e3c5e6cb-8df3-45fa-b86b-f38282140704 TB31.0 beta bp-8a33735f-ce91-4cd5-adda-e93012140710 TB24.6.0 bp-1c4d5a68-af43-48bf-993f-f621e2140710 TB24.6.0 bp-94ab0a1d-de43-47f6-96fb-4c9cd2140629 TB24.4.0 bp-4ca578a1-af32-473a-b63f-8e0a02140803 TB24.6.0 Mac bp-636d8256-ade4-464c-8b1b-282b42140728 TB24.6.0 Mac (bug 791149 covers startup crashes)
hiro do you want to take this?
Flags: needinfo?(hiikezoe)
Yes, I will take a look this. The length of mozstatus seems to be wrong.
Flags: needinfo?(hiikezoe)
(In reply to Hiroyuki Ikezoe (:hiro) from comment #2) > Yes, I will take a look this. > The length of mozstatus seems to be wrong. bp-569c017b-15dc-4378-ab94-82dcc2160107
Blocks: 791149
Summary: crash nsParseMailMessageState::FinalizeHeaders → crash nsParseMailMessageState::FinalizeHeaders due to wrong length of mozstatus
Do we have a sample message here or anything?

(In reply to :aceman from comment #4)

Do we have a sample message here or anything?

No. What do you make of bp-72c474b1-41e2-4a63-a5e9-95ccc0191109 ?

Crash Signature: [@ nsParseMailMessageState::FinalizeHeaders()] [@ nsParseMailMessageState::FinalizeHeaders ] → [@ nsParseMailMessageState::FinalizeHeaders ]
Flags: needinfo?(acelists)

So few crashes I don't think this is worth keeping. Today's crashes might not even be the same crash as originally reported.

Status: NEW → RESOLVED
Closed: 4 years ago
Depends on: 1581079
Flags: needinfo?(acelists)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.