303780 - Crash when trying to "print" to a PDF.

Status: RESOLVED WORKSFORME

(Core :: Printing: Output, defect)

Description

[phil murray]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.8) Gecko/20050511

When I try to download a page from Snopes I will print to a PDF to capture all
of the info and keep it organized. About 90% of the time I will get an alert
that Mozilla had unexpectedly quite and my choice is to click the "OK" button.
The alert will come sometimes before the PDF completes and sometimes after. 

Reproducible: Sometimes

Steps to Reproduce:
1. Find the Snopes article I wish to read. 
2. If there is a "printer" version available I will use that as it strips out
superfluous data.
3. Click "file" -> "print" -> choose "PDF" -> "print PDF."
4. Wait and a processing window will start with "printing page 1 - 2 etc"
5. Alert window stating that Mozilla has left the building ...
Actual Results:  
about 90% of the time a crash is the result.

Expected Results:  
I figure the software should have just hung on a liitle longer.

I have tried this same scenario using Safari and I don't experience the problem.

Comment 1

[Adam Guthrie]

Could you please provide a talkback ID for the crash?
http://kb.mozillazine.org/Talkback

Comment 2

[Stefan [:stefanh]]

Phil,

I assume you mean "Save as PDF"? Seems to worksforme with SeaMonkey 2005080611
on Mac OS 10.3.9. I managed to save two articles (File-->Print: "Save as PDF")
without any problems.

This issue could have been resolved (you are reporting this with a Mozilla
version made from the 1.7 branch, but lots of bugs have been fixed on the
development branch since the 1,7 branch was cut). Can you please test this with
a more recent build, like a SeaMonkey/Firefox nightly (Firefox & SeaMonkey are
using the same code for printing)? As a starter, you could try and see if the
problem exists in the latest Mozilla 1.8b release.

See also bug 220728 (old).

Comment 3

[phil murray]

updated to 1.7.11 and problem seems to be fixed.

Comment 4

[OstGote!]

(In reply to comment #3)
> updated to 1.7.11 and problem seems to be fixed.

So resolving as WFM. If you see this again feel free to reopen this bug.