Closed Bug 608521 Opened 14 years ago Closed 13 years ago

Seamonkey crashes when using print function

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jcricket, Unassigned)

References

()

Details

(Keywords: stackwanted)

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0b7pre) Gecko/20101008 Firefox/4.0b7pre SeaMonkey/2.1b1
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b7pre) Gecko/20101008 Firefox/4.0b7pre SeaMonkey/2.1b1

After starting Sudoko, press the F12 key to print solutions.  the browser crashes...

Reproducible: Always

Steps to Reproduce:
1.go to http://www.timesunion.com/sudoku/
2.start the game with hints on.  (space bar)
3.press f12
4. click ok to print


Expected Results:  
screen froze, I was able to start task manager from the task bar, and stop the program

print the solution screen
Safemode allowed me to print the sudoko page where the issue was seen.  

In normal mode, the problem occurred on yesterdays (10/30/2010)  sudoko page/puzzle  BUT did not happen on todays (10/31/2010) sudoko page/puzzle.
Possible it's a printer driver problem - I see that before.
If you ready to check this version, set any print-to-pdf driver, like cutepdf orpdfcreator, and try to print this page on that pseudo-printer.
Closing as incomplete. No reply from reporter in three months. Please reopen if you can get us a crash stack.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
This error occurs at least once each week, sometimes more. It happened on todays puzzle 2/4/11.  usually the error occurs on a puzzle that is rated 4 or 5 in difficulty.  

When it locks up I end the task using task manager, and start firefox (3.6.13) which has never encountered the problem.   

When it locks-up, the print screen is displayed, but frozen.  You cannot choose another printer, OR print the original requested screen. And after killing both the print task and the seamonkey task the system performs normally.  All other programs I use get the expected results.
You need to log in before you can comment on or make changes to this bug.