276905 - CTRL-P Crashes Firefox, Print button works [@ USER32.dll ]

Status: RESOLVED INCOMPLETE

(Core :: Printing: Output, defect)

Description

[Kevin Hecht]

Against the release version of Firefox 1.0, pressing CTRL-P repeatedly crashes
firefox.exe, using the print button works.

Reproducible behavior (on this system) seen against
http://groups-beta.google.com/group/comp.sys.laptops/browse_thread/thread/1eb0409186f27fcf/cc59ce15c3b25759
with a Ricoh Aficio 2045 PCL 6 print driver on Windows Server 2003. Press CTRL-P
to crash.

This is _not_ reproducible on a colleague's system (XP) with the same driver.
Talkback incident IDs TB2894640Y and TB2894626X for more info.

Comment 1

[Adam Hauner]

Kevin Hecht: Could you reproduce with Firefox 1.0.1? Could you please provide
actual Talkback id of your crash (previous are actually too old and were deleted)?

Comment 2

[Kevin Hecht]

New Talkback ID against 1.0.1 release is: TB4476414E

Comment 3

[Adam Hauner]

Incident ID: 4476414
Stack Signature	USER32.dll + 0x35210 (0x77d35210) ee692465
Product ID	Firefox10
Build ID	2005022304
Trigger Time	2005-03-20 09:32:21.0
Platform	Win32
Operating System	Windows NT 5.2 build 3790
Module	USER32.dll + (00035210)
URL visited	
User Comments	
Since Last Crash	62755 sec
Total Uptime	1079666 sec
Trigger Reason	Access violation
Source File, Line No.	N/A
Stack Trace 	
USER32.dll + 0x35210 (0x77d35210)
kernel32.dll + 0x244b (0x77e4244b)
kernel32.dll + 0x30abc (0x77e70abc)
USER32.dll + 0x351e6 (0x77d351e6)
USER32.dll + 0x351e6 (0x77d351e6)
USER32.dll + 0x351e6 (0x77d351e6)
USER32.dll + 0x351e6 (0x77d351e6)
USER32.dll + 0x351e6 (0x77d351e6)
USER32.dll + 0x351e6 (0x77d351e6)
except_handler3
kernel32.dll + 0x30abc (0x77e70abc)

It looks like problem outside Firefox...

Comment 4

[timeless]

except_handler3 is too late in the game. but there's a bug somewhere where i'm
planning to add try{}catch{} handling to most printing calls, but yeah, please
complain to your printer driver vendor and make sure you're using the latest driver.

Comment 5

[Kevin Hecht]

Unfortunately it's the latest driver
(http://www.ricoh-usa.com/downloads/downloads.asp?path=http://support.ricoh.com/bb/html/dr_ut_e/rc2/model/x2035_2045/x2035_2045en.htm)
and I'll complain to Ricoh.

Any handling that can be added to Firefox to better handle this would be useful.
I know FF shouldn't have to compensate for someone else's boneheaded
programming, but the average end user will blame the app that crashes. Oh well.

Comment 6

[Chris Blore]

Marking as WORKSFORME as this is not a Firefox bug

Comment 7

[timeless]

[e-mail]: erm. firefox crashes. gecko could not crash. how is this not a firefox bug?

Comment 8

[Jesse Ruderman on Windows]

timeless, did you ever add those try..catch things?  What's the bug number?

Kevin, does this still crash for you with the latest Firefox and Ricoh drivers?

Comment 9

[Kevin Hecht]

Unfortunately, I no longer have the same or equivalent hardware to test this as I reported it nearly 5 years ago. However, I have not seen any crashes via this route in FF 2.x or higher recently.

Comment 10

[timeless]

jesse: sadly, no.