454034 - FF 2.0.0.0.14 causes fatal exception 06 when using network printing off Win98SE computer

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[jminifie588t]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/2.0.0.0.14

I have 3 computers (2 laptops (WinXP Pro SP3) and 1 Desktop (Win98SE)) networked together.  An HP Deskjet 722C printer is wired to the Desktop computer which is running FF 2.0.0.0.14.  FF does not need to be active.  When I send a print job from either laptop, the desktop locks up with the following error message:
"A fatal exception 06 has occurred at 6A47:000000F4.  The current application will be terminated."

Reproducible: Always

Steps to Reproduce:
1. Turn on the Desktop running Win98SE.
2. Send print job from either laptop computer (Win XP Pro SP3) wirelessly.
3.
Actual Results:  
Computer locks up and this Error message is displayed: "A fatal exception 06 has occurred at 6A47:000000F4.  The current application will be terminated."

Expected Results:  
Expected the print job to be executed flawlessly, which happens with FF 2.0.0.0.13.

The FF software should have done nothing as FF was not active during this episode.

Comment 1

[Dave Garrett]

I don't understand how this could in any way be related to Firefox. I think you're leaving something out of the description here...

Comment 2

[jminifie588t]

I discovered, later, that before the problem occurs, I have to have opened and closed the browser.  It also appears that this issue is not limited to FF, it also occurred when I opened and closed IE6 prior to sending a print job.
Reboot doesn't clear up the conditions that lead to this problem.
The only way I know and have at my disposal is to reload an image of the C-drive that was made on 04-24-08.  I hope this may jog someone's memory so I can resolve this on my system.

Comment 3

[jminifie588t]

(In reply to comment #1)
> I don't understand how this could in any way be related to Firefox. I think
> you're leaving something out of the description here...

Please take a look at my update comment #2.  Thanks for your interest.

Comment 4

[Dave Garrett]

Ok, I still don't quite this, but it doesn't matter because:
1) Doesn't require Firefox
2) Involves an old Firefox version
3) Requires an archaic operating system
4) If an OS crashes/freezes it's always the OS's fault, even if it was triggered by something else.

Honestly, the only answer you're likely to get out of anybody is: don't use freakin' Windows 98SE. I would think any glitch you can stop with such voodoo as opening a random image file qualifies as one to flee the OS in terror. ;)

In any case, this is not a Mozilla bug and this is not a tech support forum.