Open Bug 367896 Opened 18 years ago Updated 10 years ago

messages don't show in threaded view with this 3 msg mbox (show in unthreaded view). messages that claim to be children (in-reply-to) of each other

Categories

(MailNews Core :: Backend, defect)

defect
Not set
major

Tracking

(Not tracked)

People

(Reporter: mkmelin, Unassigned)

Details

(Keywords: testcase)

As Wayne noticed with the bug 321495 attachment 207004 [details] mbox

When sorting in date order, messages show in thread pane OK
- however, in threaded mode the message thread disappears

Sorting by date and restarting makes the messages show again, but in threaded view the results are very strange.

Seen on Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2pre) Gecko/20070123 Thunderbird/2.0b2pre ID:2007012303, trunk too.
Flags: blocking-thunderbird2?
Moving off bugs that didn't make the deadline for Thunderbird 2. 
Flags: blocking-thunderbird2? → blocking-thunderbird2-
-> All/All per comment in bug 321495.
OS: Linux → All
Hardware: PC → All
Bug still present, Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b3pre) Gecko/2008012303 Lightning/0.6a1 Thunderbird/3.0a1pre ID:2008012303
Assignee: mscott → nobody
Component: Mail Window Front End → MailNews: Backend
Product: Thunderbird → Core
QA Contact: front-end → backend
Product: Core → MailNews Core
Interesting, with the testcase (on trunk) as soon as I click on the folder i crash - no breakpad or anything:(
Flags: blocking-thunderbird3?
Keywords: testcase
Summary: messages don't show in threaded view → messages don't show in threaded view with this 3 msg mbox (show in unthreaded view)
I've crashed a few times now due to bug 454053 and got breakpad showing, for this crash I still don't get any breakpad...
Magnus, the crash with the test case from bug 321495 is a stack overflow. I'm investigating it now - nsMsgHdr::GetIsKilled is recursing infinitely because of a bogus threading structure. Do you know if there's a separate bug open on that issue?
Not that I know of, no.
Ugh, bugzilla is being annoying. What we have here is two messages that claim to be children of each other, specifically, in-reply-to each other. We have been trusting of these claims up until now, but I guess we have to sanity check them.
david: please file a bug against product:bugzilla :), attach the relevant messages.
sorry, timeless, they weren't bugzilla messages; if bugzilla was doing that, it would be beyond annoying :-) clicking back from edit attachments keeps telling me it wants to repost, even though I didn't change anything, so I was losing comments.
oh! (well at least you figured out how i misinterpreted what you wrote) disable javascript (use noscript), the problem is the YUI keyword chooser.
while I'm trying to deal with various threading edge cases, I might as well try to deal with this one.
Assignee: nobody → bienvenu
Flags: blocking-thunderbird3? → blocking-thunderbird3+
Target Milestone: --- → Thunderbird 3.0b1
moving to b2
Target Milestone: Thunderbird 3.0b1 → Thunderbird 3.0b2
Target Milestone: Thunderbird 3.0b2 → Thunderbird 3.0b3
(In reply to comment #8)
> Ugh, bugzilla is being annoying. What we have here is two messages that claim
> to be children of each other, specifically, in-reply-to each other. We have
> been trusting of these claims up until now, but I guess we have to sanity check
> them.

bienvenu, this has addressed in another bug, no?
no, not the last time I checked...I think I've dealt with similar things in other bugs, where we got confused about which message was a reply to which message, but this is a case where the messages themselves are actually lying.
moving off blocking list. Would be really nice to fix, though
Flags: wanted-thunderbird3+
Flags: blocking-thunderbird3-
Flags: blocking-thunderbird3+
Assignee: mozilla → nobody
Summary: messages don't show in threaded view with this 3 msg mbox (show in unthreaded view) → messages don't show in threaded view with this 3 msg mbox (show in unthreaded view). messages that claim to be children (in-reply-to) of each other
Target Milestone: Thunderbird 3.0b3 → ---
You need to log in before you can comment on or make changes to this bug.