Closed Bug 85194 Opened 23 years ago Closed 23 years ago

MailNews Crashes upon downloading newsgroup headers - MSVCRT.DLL

Categories

(MailNews Core :: Backend, defect)

x86
Windows ME
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 82595

People

(Reporter: wd, Assigned: mscott)

Details

(Keywords: crash)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:0.9.1+) Gecko/20010611 BuildID: 2001061104 Every time I download the headers for comp.sys.ibm.pc.hardware.chips , MailNews Crashes. (MSVCRT.DLL) It appears that all the headers are downloaded, but once that's done it just crashes. Reproducible: Always Steps to Reproduce: 1.Download all headers for comp.sys.ibm.pc.hardware.chips 2. 3. Actual Results: Mozilla crashes Expected Results: no crash This may be tricky to reproduce, since everybody's NNTP servers are different, but I have 2 talkback reports: TB31577267K TB31577167Q
Keywords: crash
QA Contact: esther → stephend
If you delete your .msf for the corresponding newsgroup, does this work again?
Deleting the MSF seemed to fix it in this case. What would cause MailNews to get into this condition in the first place, though?
See bug 82595 for details. If you experience a crash again with this new .msf, please re-file. Thanks. *** This bug has been marked as a duplicate of 82595 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
From 82595 - ------- Additional Comments From bienvenu@netscape.com 2001-05-25 09:19 ------- OK, here's the problem - when messages arrive out of threading order, we have to move messages around in the thread table in order to get the first message in the thread to be the first message in the thread table. The way we do this is, if we see that a new message is the parent of an existing message, we move it before the existing message. If the existing message was the former "first message in the thread", the new message becomes the first message in the thread. However, in this case, what's happening is that the newly arrived message is a parent of the soon to be former first message in the thread, but the newly arrived message already has a parent in the thread. What needs to happen is that the oldest existing ancestor of the newly arrived message should become the root message in the thread. In most cases, that will end up being the new message, but it might be an existing message. I'll try to come up with a patch for this. verified dup.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.