61503 - Crash in msgbsutil.dll when accessing n.p.m.mail-news

Status: VERIFIED WORKSFORME

(MailNews Core :: Backend, defect, P3)

Description

[David Chamberlin]

This just started happening in the last week.  I used to be able to access
netscape.public.mozilla.mail-news no problem.  But now when I try, I keep
getting a crash in msgbsutil.dll.  More detail on the bottom of the description.

I *think* it's caused by the large number of messages available in
n.p.m.mail-news.  What happens when I access it is it asks me if I want to
download the most recent 1,000 messages.  I answer yes, then a about 10 seconds
later it crashes.  I've not had problems with any other newsgroups, even ones
where I had to download 1,000 messages.  I thought maybe it was a regression
since I used to be able to access n.p.m.mail-news, but I tried using the nov16
build which was the last build I successfully accessed that newsgroup and it
failed.

Hmmmm...I wonder if there's something corrupt in my .msf for for that group.
After I finish submitting this report I'll try removing it and trying again.

I don't know how useful any of this is, but here's the information I have.  Note
that this is with the nov27 build (I hope - if the addresses don't line up, then
I was running the nov16 build at the time).

MOZILLA caused an invalid page fault in
module MSGBSUTL.DLL at 015f:60c52e93.
Registers:
EAX=ffffffff CS=015f EIP=60c52e93 EFLGS=00010293
EBX=00000000 SS=0167 ESP=0068f9d4 EBP=0068f9f4
ECX=000027a7 DS=0167 ESI=0281eed0 FS=11ff
EDX=0068fa24 ES=0167 EDI=00000000 GS=128f
Bytes at CS:EIP:
89 43 0c 0f 8f 12 01 00 00 75 0d 51 8b cb e8 f6
Stack dump:
00000000 0281eed0 00000000 027e1e70 60614874 027e4c04 60cf712f 027e4c00 0068fa28
6061ad44 000027a7 0000280a 00000000 027e1e70 027e7c4c 60622246

I pulled up MSDuhv and got a little more info, but probably not much useful.
Here's the disassembly around the crash:

jl          60C52E61
60C52E70   mov         ecx,esi
60C52E72   call        60C529DE
60C52E77   push        1
60C52E79   pop         eax
60C52E7A   jmp         60C52CDB
60C52E7F   push        ebp
60C52E80   mov         ebp,esp
60C52E82   sub         esp,14h
60C52E85   push        ebx
60C52E86   mov         ebx,ecx
60C52E88   mov         ecx,dword ptr [ebp+8]
60C52E8B   or          eax,0FFh
60C52E8E   cmp         ecx,dword ptr [ebp+0Ch]
60C52E91   push        esi
60C52E92   push        edi
60C52E93   mov         dword ptr [ebx+0Ch],eax
60C52E96   jg          60C52FAE
60C52E9C   jne         60C52EAB
60C52E9E   push        ecx
60C52E9F   mov         ecx,ebx
60C52EA1   call        60C52B9C
60C52EA6   jmp         60C52FAE

Here's the stack trace:

MSGBSUTL! 60c52e93()
MSGNEWS! 6061ad44()
MSGNEWS! 606245c4()
MSGBSUTL! 60c5d93c()
NECKO! 60666bbd()
NECKO! 606666ce()

Comment 1

[David Chamberlin]

OK, it definitely looks like it was a corrupt .msf file.  I removed the .msf
file and it works fine now.  I looked at the .msf file in a text editor and
there's definitely some "****" at the end of the file.  If you want I can make
the file accessible on my web server for you to take a look, to try and figure
out how it got corrupted.  And/or you can just close this bug as it's working
now.  Or maybe you want to keep the bug open as a reminder that you should
handle these errors more gracefully?

Comment 2

[[e-mail] (gone - use [e-mail] instead)]

Taking this until I can find out what needs to be done with the bug.

Comment 3

[[e-mail] (gone - use [e-mail] instead)]

WFM using Windows NT 4.0, build 2000121104.  Reporter, if you want to file a bug
on us not being able to handle .msf corruptions, please do.  I'm closing this
because it's filed on us crashing, which isn't happening.  Thanks.

Comment 4

[[e-mail] (gone - use [e-mail] instead)]

VERIFIED.

Comment 5

[[e-mail] (gone - use [e-mail] instead)]

Marking VERIFIED for real, since bug 62552 was in my way.