Closed
Bug 153662
Opened 22 years ago
Closed 18 years ago
Browser Printing on W2K system causing blue screen crash
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
WORKSFORME
mozilla1.3alpha
People
(Reporter: cwcox, Unassigned)
Details
(Keywords: crash)
Attachments
(1 file)
36.00 KB,
application/octet-stream
|
Details |
Installed Netscape V6.2 and tried to print 128 bit secure web page- browser hung in spool mode indefinately. Deinstalled Netscape and installed Mozilla. Any printing of ANY web page using PRINT or PRINT PREVIEW causes a blue screen crash with a windows KMODE Exception. The printer is setup as network printer, but is local to LPT1 on the W2K system having problems with the browser. Printing works with Windows Explorer on any webpage to the same printer- XEROX WorkCentre 385.
I would like to confirm this. freshly formatted/install of win2k pro. mozilla 1.2b and nightly as of 10-15-02 cause blue-screen/reboot. Printing from anything else works.
Comment 2•22 years ago
|
||
Is it an english version of Win2k?
mine is an english version. here is my system info as reported by win2k: System Information report written at: 10/21/2002 06:18:35 AM [System Summary] Item Value OS Name Microsoft Windows 2000 Professional Version 5.0.2195 Service Pack 3 Build 2195 OS Manufacturer Microsoft Corporation System Name MANKIND System Manufacturer Micro-Star Inc. System Model MS-6215 System Type X86-based PC Processor x86 Family 6 Model 8 Stepping 10 GenuineIntel ~946 Mhz BIOS Version 01/14/02 Windows Directory C:\WINNT System Directory C:\WINNT\System32 Boot Device \Device\Harddisk0\Partition1 Locale United States User Name Total Physical Memory 260,528 KB Available Physical Memory 115,992 KB Total Virtual Memory 892,844 KB Available Virtual Memory 602,536 KB Page File Space 632,316 KB Page File C:\pagefile.sys
Comment 4•22 years ago
|
||
Was there an earlier version of 7.0 that printer? Try this: Install a printer driver for a printer you do not have (like maybe an HP), and instead of selecting "LPT1:" select "FILE:" at installation so it always prints to a file. Try printing with that. If that works, then install a new printer for "XEROX WorkCentre 385" and have it print to "FILE:" and see if that causes a crash.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Target Milestone: --- → mozilla1.2beta
I could print to the file no problem. There have been no mozilla/netscape or any other browser on this box (other than IE of course). I am using a different printer than the original poster, though. The one I am using is a NEC Superscript 1400 series. sorry forgot to mention that at the offset. David
Updated•22 years ago
|
Target Milestone: mozilla1.2beta → mozilla1.2final
I am having a similar problem on a Win2K system, Mozilla 1.0.1, Xerox Workcentre 390 printer. I get a blue screen crash (kmode_exception_not_handled) whether I am trying to print to the network printer or to a bogus local printer set to print to a file as suggested in comment #4. Printing from other apps works fine.
Comment 7•22 years ago
|
||
This attachment is a simple scaled down version of what I hope represents what we do in printing, at least the part that is responsible for dealing with the DevMode structure/object which is where I think the crash maybe coming from. Mike, please download and run the simple app: 1) Choose print to get the old style print dialog and then print, you should get a single page with "Hello World!" on it. 2) Then try printing with the second menu option "Print EX", this is the new style dialog. Again, a single page with "Hello World!" on it.
Rod, I tried the simple app - both versions of printing worked fine. That got me to experimenting a bit - I seem to be able to print blank pages and text-only pages from within Mozilla without any problems. Pages with any images at all cause a crash. Using http://www.google.com as a simple test, I tried printing - once it hung my system with the Printing/URL:/Progress dialog box up, a second time I got a blue screen with a "bad_pool_caller" error. Thanks for your help and let me know if there's anything else I can do.
Comment 9•22 years ago
|
||
was not able to reproduce in mozilla 1.1 (20020826) System Information report written at: 2002-11-05 15:35:12 [System Summary] Item Value OS Name Microsoft Windows 2000 Professional Version 5.0.2195 Service Pack 2 Build 2195 OS Manufacturer Microsoft Corporation System Manufacturer IBM System Model 2652DXG System Type X86-based PC Processor x86 Family 15 Model 2 Stepping 4 GenuineIntel ~1200 Mhz BIOS Version PhoenixBIOS 4.0 Release 6.0 for IBM ThinkPad Windows Directory C:\WINNT System Directory C:\WINNT\System32 Boot Device \Device\Harddisk0\Partition1 Locale United States Time Zone W. Europe Standard Time Total Physical Memory 785 328 KB Available Physical Memory 333 352 KB Total Virtual Memory 2 705 932 KB Available Virtual Memory 1 842 324 KB Page File Space 1 920 604 KB Page File C:\pagefile.sys
Comment 10•22 years ago
|
||
re: Comment #8 I can also print text only pages. pages with graphics will result in the reboot, though. just in case it makes a difference, the reboot also happens in phoenix 0.4. Anything else I can do to help?
Updated•22 years ago
|
Target Milestone: mozilla1.2final → mozilla1.3alpha
Comment 11•22 years ago
|
||
Has there been any update to this bug? I just installed moz 1.2.1 and the problem is still there. Thanks, David
Comment 12•22 years ago
|
||
I am buried with many other issues. I realize this is a very bad crasher, I will try to get to it sometime soon.
Keywords: crash
Comment 13•22 years ago
|
||
Don, this seems to be crashing when trying to print pages with images. Any ideas?
Comment 14•22 years ago
|
||
rock on. Im patient and know that this isnt the only thing in your life :) Thanks, David
Comment 16•18 years ago
|
||
WFM Using FF 1.5 for about 1/2 year never seen a bluescreen, nor with prior release on windows 2000. Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•