85971 - M091 Crash in local mail folder [@ nsMsgLocalMailFolder::EndCopy]

Status: VERIFIED FIXED

(MailNews Core :: Networking: POP, defect)

Description

[Scott MacGregor]

One of the folks posting comments on the CNET download page gave us a big thumbs
down because the mail client crashes for him every time he uses it. I looked up
his email address in talkback, and here's a stack trace showing where he's crashing:

Incident ID 31722995
Stack Signature nsMsgLocalMailFolder::EndCopy 29114b95
Bug ID
Trigger Time 2001-06-14 10:46:18
User Comments Man, this is the buggiest program I have ever seen. Doing the mail
thing and again it crashed.
Build ID 2001060713
Product ID Netscape6.10B1
Platform ID Win32
Stack Trace
nsMsgLocalMailFolder::EndCopy
[d:\builds\seamonkey\mozilla\mailnews\local\src\nsLocalMailFolder.cpp, line 2279]
nsCopyMessageStreamListener::EndCopy
[d:\builds\seamonkey\mozilla\mailnews\base\src\nsCopyMessageStreamListener.cpp,
line 144]
nsCopyMessageStreamListener::OnStopRequest
[d:\builds\seamonkey\mozilla\mailnews\base\src\nsCopyMessageStreamListener.cpp,
line 179]
nsMsgProtocol::OnStopRequest
[d:\builds\seamonkey\mozilla\mailnews\base\util\nsMsgProtocol.cpp, line 281]
nsMailboxProtocol::OnStopRequest
[d:\builds\seamonkey\mozilla\mailnews\local\src\nsMailboxProtocol.cpp, line 344]
nsOnStopRequestEvent::HandleEvent
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsRequestObserverProxy.cpp, line 159]

Comment 1

[Scott MacGregor]

adding keyword junk.

Comment 2

[Navin Gupta]

I think the fix may already be in. I checked it as part of another fix on 
6/8/01. It should not crash after that if i am correct. 

Comment 3

[Håkan Waara]

Jay, Navin has a hunch this crash is already fixed. Can you check when the last
talkback with this crash was reported?   Thanks

Comment 4

[Jay Patel [:jay]]

It looks like the fix worked and this crash is no longer on the Trunk (last
crash reported was with build 2001060613).  However, there are quite a few
crashes with Mozilla 0.9.1/Netscape 6.10 PR1 being reported by Talkback.  What
do we do with these kinds of crashes that are fixed on the Trunk, but are
topcrashers with a recent milestone/release?  I think this is safe to mark as
fixed, but adding M091 to summary for tracking, since this is a major crash with
our recent releases.

Comment 5

[Håkan Waara]

Navin's call to mark as fixed.

Comment 6

[Navin Gupta]

marking fixed. Nothing much can be done about beta now !!!

Comment 7

[Shiva Thirumazhusai]

This crash is NOT reported in the recent topcrash reports.(last 10 days).
Marking it as Verified.