Closed Bug 1770373 Opened 3 years ago Closed 3 years ago

Message Reader : next messages headers appended after body of current message

Categories

(Thunderbird :: Message Reader UI, defect, P2)

Thunderbird 101

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1777738

People

(Reporter: benoit.choplin, Unassigned, NeedInfo)

References

Details

(Keywords: dupeme)

Steps to reproduce:

Open Thunderbird, click on email account folder, select any HTML message with valid HTML content, but no doctype declaration nor html, head and body tags inside.

Actual results:

Randomly, the headers of the 50 - amount can vary - next messages from the inbox are appended right after the body of the message being read.

Using "Repair" on the folder fixes the issue...until it happens again (with the same messages).

Expected results:

Since the missing elements are not mandatory, only the body of the selected message should be displayed (which is what happens after repair).

Also happens with some regular plain text (UTF-8) messages (e.g.: messages from cron daemon on a server), having the first next message header and body appended to the selected message.

View source also contains the inappropriate content, so the issue seems to take place when the message is read from the (IMAP) account.

Keywords: dupeme

I think dupe of bug 1742975

(In reply to Magnus Melin [:mkmelin] from comment #2)

I think dupe of bug 1742975

Well, it seems highly similar. However :

  • repair does fix the issue for me (temporarily)
  • no related crashes
  • compacting doesn't prevent it to show up again

Benoit, this might well be an early report of symptoms as collected in bug 1777738 - the root cause suspected to be bug 1777454 where compacting actually triggers the problem (best seen with TB's AV quarantine enabled).

You could try my Bug 1777454 Comment 58 to verify <=102.0.2 vs. 102.0.3.

Severity: -- → S2
Flags: needinfo?(benoit.choplin)
Priority: -- → P2
See Also: → 1777738, 1777454

Please report back with the latest version. Marking as dupe of bug 1777738 though.

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.