Closed Bug 1832698 Opened 2 years ago Closed 1 years ago

Message list with Unified Folders is not always populated

Categories

(Thunderbird :: Folder and Message Lists, defect, P2)

Thunderbird 114

Tracking

(thunderbird115 fixed)

RESOLVED FIXED
116 Branch
Tracking Status
thunderbird115 --- fixed

People

(Reporter: aleca, Assigned: darktrojan)

References

(Blocks 1 open bug)

Details

(Keywords: regression, Whiteboard: [Supernova3p][datalossy])

Attachments

(1 file)

STR:

  • Be in Unified Folder mode
  • Select Inbox
    • The message list only populates with a single message
  • Open Inbox and select the account name
    • The message list is fully populated
  • Select Inbox again
    • The message list is now populated correctly
Version: unspecified → Thunderbird 114
Severity: -- → S3
Priority: -- → P2

users may interpret this as dataloss and panic.

Severity: S3 → S2
Priority: P2 → P1
Whiteboard: [Supernova3p] → [Supernova3p][datalossy]

This is a bit tricky and I can still reproduce it.
Magnus, would you be able to figure this out?

Flags: needinfo?(mkmelin+mozilla)
Keywords: regression

Lowering the priority since nobody seems to be able to reproduce it. It still happens to me randomly.

Flags: needinfo?(mkmelin+mozilla)
Priority: P1 → P2

Has bug 1837368 made any difference?

I see this on beta. I don't currently have a nightly to test.

(In reply to Geoff Lankow (:darktrojan) from comment #4)

Has bug 1837368 made any difference?

Note, 1837368 is not yet on beta.

I'm reproducing it (or at least something strongly similar and probably with the same root cause) on the latest nightly build (20230614).

When I open nightly and don't have unread messages in my inbox the message list looks fine. But if I do have at least one unread message waiting for me then it lists only the latest unread message.

Note that this only seems to work for new unreads, if I close nightly and reopen it the list looks fine again, even if I haven't read the message.

By coincidence I've found a reliable way to reproduce this, and I now have some idea what's going on.

Assignee: nobody → geoff
Status: NEW → ASSIGNED

The block after this line is comparing a descending list of keys against an ascending list of keys,
deciding they are different, and throwing them all out.

Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/e1b348a5c07b
Stop nsMsgQuickSearchDBView::OnSearchDone discarding valid results. r=babolivier

Status: ASSIGNED → RESOLVED
Closed: 1 years ago
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch

Comment on attachment 9339433 [details]
Bug 1832698 - Stop nsMsgQuickSearchDBView::OnSearchDone discarding valid results. r=babolivier

[Approval Request Comment]
Regression caused by (bug #): ancient history
User impact if declined: message list can appear empty when it shouldn't
Testing completed (on c-c, etc.): landed yesterday
Risk to taking this patch (and alternatives if risky): low

Attachment #9339433 - Flags: approval-comm-beta?

Comment on attachment 9339433 [details]
Bug 1832698 - Stop nsMsgQuickSearchDBView::OnSearchDone discarding valid results. r=babolivier

[Triage Comment]
Approved for beta

Attachment #9339433 - Flags: approval-comm-beta? → approval-comm-beta+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: