146780 - Crash-cancel Print dialog when printing News msg with attached files if cache set to nothing

Status: RESOLVED DUPLICATE of bug 159995

(MailNews Core :: Printing, defect, P5)

Description

[esther]

Using branch build 20020522 on winxp I get a crash (talkback incident 5862104)
if I have my disk and memory cache set to nothing, canceling the Print dialog of
a news posting with attachment, will crash.

1. Launch app
2. Remove values for Disk and Memory Cache in preferences
3. Launch mail open newsgroup news.public.test, select news posting by Stephen
Donner titled "testing images (save to disk), dated 5-20-2002 lines=8710.
4. After it loads (images don't display), click Print.
5. Status reads loading images to print, when finished, Print dialog comes up
(30sec to 1 minute). Cancel the Print and Crash

Result: Crash
Expected: msg to print

Comment 1

[esther]

Note: if this same news posting is copied to my IMAP folder and I run through
this scenario from there I don't crash and the images do display. 

Comment 2

[esther]

Stack Trace from talkback
MimeGetAttachmentList
[d:\builds\seamonkey\mozilla\mailnews\mime\src\mimemoz2.cpp, line 532]
mime_display_stream_complete
[d:\builds\seamonkey\mozilla\mailnews\mime\src\mimemoz2.cpp, line 921]
nsStreamConverter::OnStopRequest
[d:\builds\seamonkey\mozilla\mailnews\mime\src\nsStreamConverter.cpp, line 1017]
nsImapCacheStreamListener::OnStopRequest
[d:\builds\seamonkey\mozilla\mailnews\imap\src\nsImapProtocol.cpp, line 6995]
nsStorageTransport::nsReadRequest::OnStopRequest
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsStorageTransport.cpp, line 609]
XPTC_InvokeByIndex
[d:\builds\seamonkey\mozilla\xpcom\reflect\xptcall\src\md\win32\xptcinvoke.cpp,
line 106]
EventHandler [d:\builds\seamonkey\mozilla\xpcom\proxy\src\nsProxyEvent.cpp, line
567]
PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 597]
PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c,
line 530]
_md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line
1078]
USER32.dll + 0x3c076 (0x77d7c076)
USER32.dll + 0x3c076 (0x77d7c076)
_except_handler3()
kernel32.dll + 0x3bb86 (0x77e9bb86) 

Comment 3

[esther]

Talkback incident is NOT the one listed above 5862104, the talkback for this
crash hasn't come in yet.  Sorry. 

Comment 4

[esther]

Here is the correct talkback incident 6607154 and stack 0x00020027 46637624:
0x00020027 
nsDocLoaderImpl::doStopDocumentLoad
[d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp, line 771]
nsDocLoaderImpl::DocLoaderIsEmpty
[d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp, line 669]
nsDocLoaderImpl::OnStopRequest
[d:\builds\seamonkey\mozilla\uriloader\base\nsDocLoader.cpp, line 600]
nsLoadGroup::RemoveRequest
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsLoadGroup.cpp, line 531]
imgRequestProxy::OnStopRequest
[d:\builds\seamonkey\mozilla\modules\libpr0n\src\imgRequestProxy.cpp, line 392]
imgRequest::OnStopRequest
[d:\builds\seamonkey\mozilla\modules\libpr0n\src\imgRequest.cpp, line 647]
ProxyListener::OnStopRequest
[d:\builds\seamonkey\mozilla\modules\libpr0n\src\imgLoader.cpp, line 695]
nsMsgProtocol::OnStopRequest
[d:\builds\seamonkey\mozilla\mailnews\base\util\nsMsgProtocol.cpp, line 344]
nsNNTPProtocol::OnStopRequest
[d:\builds\seamonkey\mozilla\mailnews\news\src\nsNNTPProtocol.cpp, line 1245]
nsOnStopRequestEvent::HandleEvent
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsRequestObserverProxy.cpp, line 213]
PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 597]
PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c,
line 530]
_md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line
1078]
USER32.dll + 0x3c076 (0x77d7c076)
USER32.dll + 0x3c076 (0x77d7c076)
_except_handler3()
kernel32.dll + 0x3bb86 (0x77e9bb86) 

Comment 5

[esther]

Note, does not happen on linux and mac 9.1

Comment 6

[dcone (gone)]

->

Comment 7

[rods (gone)]

It shouldn't crash, but there is a general problem with printing when there is
no cache. This is a dup of a more general issue.

Comment 8

[(not reading, please use [e-mail] instead)]

it's a dup of bug #159995, fix in hand.

*** This bug has been marked as a duplicate of 159995 ***

Comment 9

[[:Aureliano Buendía]]

Cleanup *dupeme* whiteboard flag from bugs that are marked as Resolved
Duplicate!