Closed
Bug 74083
Opened 24 years ago
Closed 24 years ago
crash when printing on mac
Categories
(Core :: Printing: Output, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: saari, Assigned: dcone)
References
()
Details
(Keywords: crash)
Attachments
(2 files)
944 bytes,
patch
|
Details | Diff | Splinter Review | |
1.58 KB,
patch
|
Details | Diff | Splinter Review |
Attempt to print any page on Mac and we crash in DocumentViewerImpl:PrintPage
Comment 1•24 years ago
|
||
I get a crash whenever I print.
It seems that the first page is actually sent to the print driver, then all the
subsequent pages are blank.
After the "printing" message disappears, Mozilla crashes.
A stacktrace is attached to bug 74332, which indicates that the same stacktrace
occurrs in other crash situation in addition to printing.
Printing test should be included in Smoketests, IMHO.
Severity: normal → critical
Keywords: crash
Assignee | ||
Comment 2•24 years ago
|
||
Comment 3•24 years ago
|
||
Check for mTimer not being null after doCreateInstance and before calling
mTimer->Init, and consolidate the two calls to
mTimer->Init(this, mDelay, NS_PRIORITY_NORMAL, NS_TYPE_ONE_SHOT);
into one (like a new fcn InitTimer()?) and sr=attinasi
Assignee | ||
Comment 4•24 years ago
|
||
Comment 5•24 years ago
|
||
Don, do you need to create a new timer each time, or just re-initialize it?
sr=attinasi
Assignee | ||
Comment 6•24 years ago
|
||
you have to create a new timer.. mac.. seems re-initialization works.. but PC..
you need a new timer.
Comment 7•24 years ago
|
||
Comment 10•24 years ago
|
||
WFM in 2001041212 Mac trunk build.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Comment 11•24 years ago
|
||
This was fixed.. not really a Works for me.. I was verifing this problem..
I am going to reopen.. and then mark fixed.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Assignee | ||
Comment 12•24 years ago
|
||
Fixed
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•