trying to print will always shut down Mozilla

VERIFIED WORKSFORME

Status

()

Core
Printing: Output
--
critical
VERIFIED WORKSFORME
16 years ago
16 years ago

People

(Reporter: Larrt B, Assigned: rods (gone))

Tracking

({crash, stackwanted})

Trunk
x86
Windows 98
crash, stackwanted
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
MOZILLA caused a general protection fault
in module HPW8MON.DLL at 0003:000099eb.
Registers:
EAX=4def0000 CS=85e7 EIP=000099eb EFLGS=00000a92
EBX=0000092a SS=6277 ESP=00007242 EBP=00007252
ECX=00000017 DS=2f97 ESI=00000090 FS=0000
EDX=83c785cf ES=85cf EDI=000099b0 GS=0000
Bytes at CS:EIP:
26 8b 51 0a 89 46 f6 89 56 f8 f6 c4 08 74 18 c7 
Stack dump:
035985af 627702db 08006b98 00000000 3bb672c4 0090862f a10185cf 864f266c 00000000
86500000 729c0001 72840000 0000df54 00010000 000183c7 86500000

Comment 1

16 years ago
Which build?
What Printer?
Printer-Driver-Version?
USB / Centronix / Whatever?
Network-Printer?

Have no printing-problems with
Mozilla/5.0 (Windows; U; Win98; de-DE; rv:1.1a+) Gecko/20020702
and all my printers: HP895Cxi (USB/parallel), FRITZ-Fax, several
postscript-Printers.
Summary: trying to print will always shut down Mozilla → trying to print will always shut down Mozilla

Comment 2

16 years ago
And don't forget to post the Talkback ID here (run talkback.exe into the
Mozilla\components directory). The register/stack dump you provided doesn't have
any practical debugging usage.
Severity: normal → critical

Updated

16 years ago
Keywords: crash, stackwanted
Summary: trying to print will always shut down Mozilla → trying to print will always shut down Mozilla

Comment 3

16 years ago
Resolving as we have no reply from reporter.
Reporter, if you still have this issue in a current build, please reopen and
comment with details, including Talkback ID and printer info.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME

Comment 4

16 years ago
bulk verification.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.