Closed Bug 289612 Opened 19 years ago Closed 19 years ago

Repeatable crash when printing [@ CoreGraphics.203.30.0 + (00071cd8)]

Categories

(Camino Graveyard :: Printing, defect)

Product:
Camino Graveyard
Component:
Printing
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: tmeadow, Assigned: mikepinkerton)

References

(
URL
)

Details

(Keywords: crash)

Crash Data

Attachments

(4 files)

Apple crash reporter info
12.82 KB, text/plain
Details
Apple crash reporter info
13.43 KB, text/plain
Details
talkback-public stack from Anthony's latest crash, TB7240755M
2.32 KB, text/plain
Details
CrashReporter for repeated Camino crash
35.39 KB, text/plain
Details 
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050404 Camino/0.8+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050404 Camino/0.8+

It crashes every time I've tried this. I don't recall this problem in 0.82 or
earlier - haven't tried 0.83 though. I don't know if the page is badly formed.
IE 5.2 Mac does not have a problem with this page nor does Firefox 1.0.2 Windows.

Reproducible: Always

Steps to Reproduce:
1.Go to the url <http://track.dhl-usa.com/TrackByNbr.asp>
2.Enter a tracking number
3.Print

Actual Results:  
crash (and crash log reporter has sent in 3 reports about this crash).

Expected Results:  
print!
I tried it again so I could get the talkback #s. They are:
TB4864143Q
TB4864193E
TB4944579M
TB4946379X

(Suggestion - could the Talkback folks make it possible to copy the tracking #s
so I don't have to do these by hand?)
*** Bug 289620 has been marked as a duplicate of this bug. ***
which faq did you read that didn't explain how to do it?
http://www.mozilla.org/quality/bug-writing-guidelines.html tries to on some
platforms (ok, it doesn't for osx)

the path will be something like:
/Applications/Camino.app/Contents/MacOS/components/talkback/Talkback.app
URL: http://http://track.dhl-usa.com/Track... → http://track.dhl-usa.com/TrackByNbr.asp
Keywords: stackwanted
sorry, wrong bug. :(~
(In reply to comment #0)


Would it be possible to get some sample tracking numbers to test this with?
I only have one: 17765168525 (that's my failed g5 midplane being returned to the
factory)!
Thanks for the tracking #.  Unfortunately, it didn't crash for me when I printed
the Tracking Results page, Camino 20050417 (0.8+), Mac OS X 10.3.7, HP LJet 1300.

Will you check again with a more recent build; the early April nightlies were a
mess due to some trunk changes.  If it crashes, please *attach* (not paste into
the comments) the output of the Crash Reporter dialogue ("Camino crashed...do
you want to submit this report to Apple"; click on "submit...", paste the
results into a plain-text file).
I updated to the latest nightly build (2005041708), went to the dhl site and
used the tracking number I provided you earlier. When I tried to print and save
as pdf Camino crashed. Attached is the data from the Apple Crash Reporter. The
Talkback incident ID is TB5201606E. I'm going to try it with a couple of
regular printers next.
I just tried printing the DHL tracking results for the same tracking # to a
regular printer (Savin C3210) and it crashed this time too. Talkback incident
TB5201779Q. Let me know if you need more info.
Incident ID: 5201779
Stack Signature	CoreGraphics.203.30.0 + 0x71cd8 (0x93641cd8) 88778923
Product ID	CaminoTrunk
Build ID	2005041708
Trigger Time	2005-04-19 09:16:11.0
Platform	MacOSX
Operating System	Darwin 7.8.0
Module	CoreGraphics.203.30.0 + (00071cd8)
URL visited	
User Comments	
Since Last Crash	485 sec
Total Uptime	615 sec
Trigger Reason	SIGSEGV: Segmentation Violation: (signal 11)
Source File, Line No.	N/A
Stack Trace 	
CoreGraphics.203.30.0 + 0x71cd8 (0x93641cd8)
0x44242442
CoreGraphics.203.30.0 + 0x55e58 (0x93625e58)
CoreGraphics.203.30.0 + 0x13eb64 (0x9370eb64)
libPDFRIP.A.dylib.203.27.0 + 0x12cf4 (0x91b22cf4)
libPDFRIP.A.dylib.203.27.0 + 0x13104 (0x91b23104)
libPDFRIP.A.dylib.203.27.0 + 0x113ac (0x91b213ac)
libPDFRIP.A.dylib.203.27.0 + 0x12024 (0x91b22024)
CoreFoundation.299.35.0 + 0xf34 (0x90190f34)
libPDFRIP.A.dylib.203.27.0 + 0x64f4 (0x91b164f4)
libPDFRIP.A.dylib.203.27.0 + 0x52d0 (0x91b152d0)
libPDFRIP.A.dylib.203.27.0 + 0x5214 (0x91b15214)
libConverter.dylib.1.0.0 + 0x3768 (0x882a3768)
libConverter.dylib.1.0.0 + 0xaa14 (0x882aaa14)
PrintCore.1.0.0 + 0x1e98c (0x916fe98c)
PrintCore.1.0.0 + 0x1e900 (0x916fe900)
Print.1.0.0 + 0x16fa4 (0x91906fa4)
nsDeviceContextSpecX::EndPage() 
[/builds/camino-release/camino/trunk/mozilla/gfx/src/mac/nsDeviceContextSpecX.cpp,
line 157]
nsDeviceContextMac::EndPage() 
[/builds/camino-release/camino/trunk/mozilla/gfx/src/mac/nsDeviceContextMac.cpp,
line 848]
nsSimplePageSequenceFrame::PrintNextPage() 
[/builds/camino-release/camino/trunk/mozilla/layout/generic/nsSimplePageSequence.cpp,
line 883]
nsPrintEngine::PrintPage() 
[/builds/camino-release/camino/trunk/mozilla/layout/printing/nsPrintEngine.cpp,
line 3575]
nsPagePrintTimer::Notify() 
[/builds/camino-release/camino/trunk/mozilla/layout/printing/nsPagePrintTimer.cpp,
line 86]
nsTimerImpl::Fire() 
[/builds/camino-release/camino/trunk/mozilla/xpcom/threads/nsTimerImpl.cpp, line
387]
handleTimerEvent() 
[/builds/camino-release/camino/trunk/mozilla/xpcom/threads/nsTimerImpl.cpp, line
451]
PL_HandleEvent() 
[/builds/camino-release/camino/trunk/mozilla/xpcom/threads/plevent.c, line 699]
PL_ProcessPendingEvents() 
[/builds/camino-release/camino/trunk/mozilla/xpcom/threads/plevent.c, line 633]
CoreFoundation.299.35.0 + 0x3d68 (0x90193d68)
CoreFoundation.299.35.0 + 0x1540 (0x90191540)
CoreFoundation.299.35.0 + 0x5e6c (0x90195e6c)
HIToolbox.145.0.0 + 0x5f60 (0x927d5f60)
HIToolbox.145.0.0 + 0xc640 (0x927dc640)
HIToolbox.145.0.0 + 0x2e6a0 (0x927fe6a0)
AppKit.743.33.0 + 0x12e44 (0x92dd2e44)
AppKit.743.33.0 + 0x298c8 (0x92de98c8)
AppKit.743.33.0 + 0x3dc30 (0x92dfdc30)
AppKit.743.33.0 + 0xfa2b8 (0x92eba2b8)
PR_Free()   start()
Severity: normal → critical
Keywords: stackwanted → crash
Summary: Repeatable crash when printing → Repeatable crash when printing [@ CoreGraphics.203.30.0 + (00071cd8)]
I am also unable to duplicate the crash.  I'm on a Dual-G5 1.8Ghz, OS 10.3.9,
millions of colors.  Simon or Mike, can you guys duplicate the crash?
WFN me aswell.
Anthony, can you please test this again with a recent nightly?  I just tried
again and it is still WFM.
*** Bug 295523 has been marked as a duplicate of this bug. ***
In the new dupe (bug 295523), Anthony got the crash again today with the
20050704 build and the Yahoo URL in that bug; pretty much identical stack.  I
still can't repro :-(

Anthony, is there anything "different" or "odd" about your configuration?
Javier, Simon, Mike: I was just looking through talkback-public, trying to see
if perhaps this and (the crashing part of) bug 286176 were the same.

I noticed there are 98 incidents for CaminoTrunk that have CoreGraphics as their
signature (across 10.2, 10.3, 10.4), and the comments in a number of them
mention printing or saving as PDF:
http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=1&searchby=stacksig&match=contains&searchfor=CoreGraphics&vendor=All&product=CaminoTrunk&platform=All&buildid=&sdate=&stime=&edate=&etime=&sortby=bbid

I don't know what constitutes a topcrash for Camino (the topcrash report for
Camino at talkback-public doesn't work) or whether those reports or the URLs in
the comments of those URLs will help or not; just providing some more info....
Repeatable crash at  http://www.santacruzcourt.org/applic1.pdff
Running Mac OS X 10.4.2  Prints fine in Safari 2.0
This crash shows the PDF Browser Plugin crashing, not Camino.
That's Quartz crashing. Preview also crashes trying to print the above PDF.
It would not surprise me if this bug (i.e., comment 0-comment 16) is the same as
the one reported in bug 301720.
Anthony, can you still get the crash (either with this URL or the one from bug bug 295523) in 1.0b2?

There used to be a fair number of similar stacks in Talkback, but I'm only seeing a couple (and none that mention printing/saving PDF) these days, so Sam and I were wondering if something changed in the Core or the OS to make this WFM.
Since I've started using the 1.0x series of releases I have not seen this bug. I saw it relatively frequently when using the 0.8x releases of Camino.
OK, based on that info and the Talkback data (and the fact that none of the devs nor QA people could ever repro), I'm going to close this WFM.

Anthony, if it ever pops up again (with a similar crashlog), please reopen this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
Crash Signature: [@ CoreGraphics.203.30.0 + (00071cd8)]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: