Closed Bug 75893 Opened 24 years ago Closed 24 years ago

crash printing this and a lot of other sites.

Categories

(Core :: Printing: Output, defect)

PowerPC
Mac System 9.x
defect
Not set
critical

Tracking

()

VERIFIED FIXED
mozilla0.9

People

(Reporter: tarahim, Assigned: dcone)

References

()

Details

(Keywords: crash, Whiteboard: need for 0.9 - eta 4/24)

Attachments

(5 files)

2001041212 Mac trunk. Even though bug 74083 is now WFM, this URL page crashes before Mozilla starts to send data to printer driver. Steps to reproduce: Goto URL Print (Just print entire document without any option) Result:crash.
I am crashing trying to print various pages at CNN.com, wasingtonpost.com, etc with the same stack trace.
nominating for 0.9, adding crash keyword
Keywords: crash
Summary: crash printing this URL. → crash printing this and a lot of other sites.
Target Milestone: --- → mozilla0.9
I can reproduce on the Mac.. but.. the "and a lot of other sites." does not help. What are these sites.. do they have things in common. Are they top 100 sites. That would help in the disposition of this bug. Currently. it blows up deep in layout, I have not a clue where.. and the url is huge. the test case needs to be minimized
Actually, http://news.bbc.co.uk does crash, if I try to print using FaxStf insted of LaserWriter.(see the stack trace) When printed using LaserWriter, news.bbc.co.uk comes out as mostly blank, with only the footer (not HTML footer) and the column of right side in the second page.
I can generalize the problem like this: 1.Printing crahses in various sites with tables. 2.If it does not crash (http://news.bbc.co.uk, http://www.fifa.com), the main text and a lot of the content are not printed. This may be a separate bug or the same bug. 3.The crash using preview of Faxstf is a separate bug, since USA Today crashes in both Faxstf and LW with different timing and stack traces.
Thanks for the Info.. this helps alot
*** Bug 76637 has been marked as a duplicate of this bug. ***
unsetting Target Milestone, adding nomination keyword. Nominating is done with Keywords, not Target Milestone. Target Milestone is used by the developer to communicate the development cycle in which he intends to fix the problem.
Keywords: mozilla0.9
Target Milestone: mozilla0.9 → ---
Setting target milestone to mozilla0.9. This is Don's top priority.
Target Milestone: --- → mozilla0.9
Whiteboard: need for 0.9 - need estimated eta
Whiteboard: need for 0.9 - need estimated eta → need for 0.9 - eta 4/24
Attached patch part 1 patchSplinter Review
Attached patch part 2 of patchSplinter Review
Attached patch Part 3 of patchSplinter Review
Please fix the tabs in nsSimplePageSequence.cpp, and comment about the mSpec magic in the DeviceContextMac stuff. Also, what testing have you done? sr=attinasi.
In patch1 could you just remove this code instead of removing 1 line and leaving the rest of the code commented out. The remaining code will be confusing to look at. //if (nsnull == mSurface) - aSupportsWidgets = PR_TRUE; + //else //aSupportsWidgets = PR_FALSE; Please add a NS_WARNING when EndPage indicates a failure. if(mSkipPageEnd){ + PRINT_DEBUG_MSG1("***************** End Page (DoPageEnd) *****************\n"); + nsresult rv = dc->EndPage(); + if (NS_FAILED(rv)) { + return rv; + } Please fix tab/spacing on the patches With the above changes r=kmcclusk@netscape.com
a=chofmann
Checked in all the fixes for this. Framesets will now print, and the sites with comboboxes should now work. Also Frameset pages could go into an endless loop with will no longer happen. Much improvement on the Mac with these fixes.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
verified. But, it is not printing properly yet. Another bug, I guess.
Status: RESOLVED → VERIFIED
hirata masakazu: Did you mean the issue described in bug 77733 ?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: