133919 - [REPRO]Crash: Printing with Ctrl+P causes reboot (mozilla0.9.9)

Status: VERIFIED DUPLICATE of bug 132216

(Core :: Printing: Output, defect)

Description

[pbotsas]

I'm trying to print a page with/without frames.

If I start print via the print-button the action is stopped.
If I start the process via Ctrl+P I can select a printer but clicking on OK
causes a reboot.

My current configuration is:
Mozilla 0.9.9 Build ID: 2002031104
Windows 2000 Pro
Language: German
Theme: Pinball

Comment 1

[Valerio Capello]

confirmed on v0.9.9+ build 2002032503 pinball win98 italian

for CTRL+P with frames only (I've tested it on http://www.elfqrin.com/hack/
which has two frames), while it printed a page without frames. However Mozilla
crashed but the system didn't reboot.

Retrieve TalkBack ID TB4557598H

Severity should be changed to critical and Crash should be added at the
beginning of the Summary.

Comment 2

[Olivier Cahagne]

Stephen, can you retreive Talkback data please: TB4557598H ?

Comment 3

[pbotsas]

I've tried it also on a non-frames page (www.pimboli.de) and the system crashed.

Comment 4

[Valerio Capello]

I couldn't reproduce this problem every time, however I confirm it also on
Mozilla v0.9.9+ build 2002032708 Modern on Win98 italy

TalkBack ID TB4567973Q

1. I opened http://www.ElfQrin.com/hack/
2. Without selecting any frame (without clicking on the mouse anywhere) I
pressed CTRL+P
3. The default option was "Print Each frame separately" and I left it unchanged
4. I pressed OK

then it crashed.

Comment 5

[Matthias Versen [:Matti]]

What do you mean with reboot ?
A win2k crash/hang, a Blue screen or a simple reboot ?

Comment 6

[sujay]

can we remove "reboot" from the summary and add "crash" ?

also try a newer build guys....

Comment 7

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

js_Interpret [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 1269]
js_Execute [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 970]
JS_ExecuteScript [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 3260]
nsJSContext::ExecuteScript
[d:\builds\seamonkey\mozilla\dom\src\base\nsJSEnvironment.cpp, line 824]
nsXULDocument::ExecuteScript
[d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULDocument.cpp, line 6196]
nsXULDocument::LoadScript
[d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULDocument.cpp, line 5988]
nsXULDocument::ResumeWalk
[d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULDocument.cpp, line 5767]
nsXULDocument::EndLoad
[d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULDocument.cpp, line 1672]
XULContentSinkImpl::DidBuildModel
[d:\builds\seamonkey\mozilla\content\xul\document\src\nsXULContentSink.cpp, line
537]
nsExpatDriver::DidBuildModel
[d:\builds\seamonkey\mozilla\htmlparser\src\nsExpatDriver.cpp, line 881]
nsParser::DidBuildModel
[d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line 1251]
nsParser::ResumeParse [d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp,
line 1790]
nsParser::OnStopRequest
[d:\builds\seamonkey\mozilla\htmlparser\src\nsParser.cpp, line 2441]
nsDocumentOpenInfo::OnStopRequest
[d:\builds\seamonkey\mozilla\uriloader\base\nsURILoader.cpp, line 255]
nsJARChannel::OnStopRequest
[d:\builds\seamonkey\mozilla\netwerk\protocol\jar\src\nsJARChannel.cpp, line 609]
nsOnStopRequestEvent::HandleEvent
[d:\builds\seamonkey\mozilla\netwerk\base\src\nsRequestObserverProxy.cpp, line 213]
PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line 591]
PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c,
line 524]
_md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c, line
1072]
KERNEL32.DLL + 0x242e7 (0xbff942e7)
0x00648c16 

Comment 8

[Olivier Cahagne]

wfm using build 2002032708 on Win2k, reproducing steps from comment #4. Printer
was an HP network printer.

Comment 9

[TucsonTester3]

I was still having the same problem on build 20020327.  It does not matter how I
try to print everytime it is the same results.  I've tried to print several
different websites and all attempts end with a crash.  I don't have to restart
but it does end the application.  


talk back id: TB45729582

Comment 10

[rods (gone)]

try with a recent trunk build and see if it is still doing it.

Comment 11

[timeless]

bug 132216 comment 40

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

Comment 12

[sujay]

verified.