crash nsParseMailMessageState::FinalizeHeaders due to wrong length of mozstatus

NEW
Unassigned

Status

MailNews Core
Backend
--
critical
3 years ago
2 years ago

People

(Reporter: wsmwk, Unassigned)

Tracking

(Blocks: 1 bug, {crash})

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

3 years ago
+++ 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)
(Reporter)

Comment 1

3 years ago
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)
See Also: → bug 973316
(Reporter)

Comment 3

2 years ago
(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
See Also: bug 791149
Summary: crash nsParseMailMessageState::FinalizeHeaders → crash nsParseMailMessageState::FinalizeHeaders due to wrong length of mozstatus

Comment 4

2 years ago
Do we have a sample message here or anything?
You need to log in before you can comment on or make changes to this bug.