Closed Bug 441350 Opened 16 years ago Closed 15 years ago

Second print attempt crashes firefox 3.0 [@ libobjc.A.dylib@0x15688 - CanonIJPDE@0x1531e]

Categories

(Core :: Printing: Setup, defect)

1.9.0 Branch
PowerPC
macOS
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 460963

People

(Reporter: n.wipfli, Unassigned)

References

Details

(Keywords: crash)

Crash Data

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0

The second print attempt for the same page, crashes firefox.

Reproducible: Sometimes

Steps to Reproduce:
1. Control-P
2. Click on cancel.
3. Control-P and this crashes firefox.
Actual Results:  
Firefox crashes.

Expected Results:  
Open the print window.
This WFM using Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0. If you have any extensions installed, trying started in safe mode.
WFM: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0
in Firefox 3.0.1 Command-P multiple times works fine.  After print dialog comes for the first time, many things in the menu are grayed out that should not be, including the entire View menu.  Fresh install of 3.0.1 on Intel Mac OS X 10.5
This happened also for me in 3.0 on another machine, also Intel Mac OS X 10.5 without crash, so might need to report separate bug.
For anyone who comes here that has the same problem as me, there was already a bug report at bug 425844
@Reporter, we have not heard back from you in a while, so I am closing this bug as INCOMPLETE. You can reopen this bug if more information becomes available. Some helpful information you can provide us is found at http://quality.mozilla.org/bug-writing-guidelines. You should also use a recent version of Firefox, from http://www.getfirefox.com.
Severity: major → critical
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Keywords: crash
Resolution: --- → INCOMPLETE
Version: unspecified → 3.0 Branch
Status: RESOLVED → UNCONFIRMED
Resolution: INCOMPLETE → ---
Hi, this bug isn't resolved yet, I'm using 3.0.7 and still have the same issue as describes initially. Everytime it crashes, it opens the crash report which I send with all the details. I do not know where this crash report goes.
It happened again right now and I've sent the crash report through the reporter tool. Here is some information but it doesn't include the complete report:

Add-ons: {972ce4c6-7e08-4474-a285-3208198ce6fd}:3.0.7,Foxdie@tanjihay.com:3.0.1,FoxdieGraphite@tanjihay.com:3.0.1
BuildID: 2009021906
CrashTime: 1237442347
InstallTime: 1237049548
ProductName: Firefox
SecondsSinceLastCrash: 309503
StartupTime: 1237132851
Theme: classic/1.0
URL: https://bugzilla.mozilla.org/process_bug.cgi
Vendor: Mozilla
Version: 3.0.7

This report also contains technical information about the state of the application when it crashed.
Thanks. Give me a few days to read the info on this link and collect the stack trace. I'll update this bug later.
This consistently happens to me as well.  Below are the details from my most recently submitted crash report (http://crash-stats.mozilla.com/report/index/7691d2bb-9a7f-4b1d-9230-d09d32090319?p=1)...

Signature: libobjc.A.dylib@0x15688
UUID: 7691d2bb-9a7f-4b1d-9230-d09d32090319
Time: 2009-03-19 05:14:56.156342
Uptime: 154
Last Crash: 309715 seconds before submission
Product: Firefox
Version: 3.0.7
Build ID: 2009021906
Branch: 1.9
OS: Mac OS X
OS Version: 10.5.6 9G55
CPU: x86
CPU Info: GenuineIntel family 6 model 15 stepping 11
Crash Reason: EXC_BAD_ACCESS / KERN_PROTECTION_FAILURE
Crash Address: 0x94604688
User Comments: Was running Firefox in safe mode with all settings set to default.
Summary: Second print attempt crashes firefox 3.0 → Second print attempt crashes firefox 3.0 [@ libobjc.A.dylib@0x15688 ]
The stack trace is now available at http://crash-stats.mozilla.com/report/index/6b0bf036-121a-4d79-b0a1-492022090319?p=1.
Stack trace ID 6b0bf036-121a-4d79-b0a1-492022090319.

Let me know if you need anything else.

Thanks
Nicolas
And that is the same as the one above, so thanks. We have that. Can you create a new profile, and see if it happens there http://support.mozilla.com/kb/Profiles
Yes it happens with a new profile too. I've just created the new profile "test" and I'm able to reproduce the issue.

http://crash-stats.mozilla.com/report/index/e1ca6288-87ad-4568-a75b-2890f2090320
(In reply to comment #14)
> Yes it happens with a new profile too. I've just created the new profile "test"
> and I'm able to reproduce the issue.
> 
> http://crash-stats.mozilla.com/report/index/e1ca6288-87ad-4568-a75b-2890f2090320

This is good information, however testing on a PPC mac with both 10.4 and 10.5, with both 3.0.7 and current trunk builds, I still can't reproduce this issue on any of those configurations.  Are you using different steps from those listed in Comment 0?
At the time I logged this bug I was using a PPC, now I'm using and can reproduce this issue on two different Mac both running 10.5 on Intel.
The first is an iMac, the second is a MacBook Pro. And it seems that bugzilla also reproduced this issue above with a Mac intel, look at his stack trace.
(In reply to comment #16)
> At the time I logged this bug I was using a PPC, now I'm using and can
> reproduce this issue on two different Mac both running 10.5 on Intel.
> The first is an iMac, the second is a MacBook Pro. And it seems that bugzilla
> also reproduced this issue above with a Mac intel, look at his stack trace.
Nicolas, this is great information.  Thanks!  However, you missed the question I asked: are you reproducing this with the steps in comment 0?  Or do you have other steps?  I can't reproduce this at all on any mac/os combination :(
Hi Clint, sorry for not responding to your other query.
Yes, I'm reproducing this issue with exactly the same steps which I've also copied below:

1. Control-P
2. Click on cancel.
3. Control-P and this crashes firefox.
I believe this issue is related to the printer driver in use. I have a Canon MP240, and was having the same issue (10.5 on Intel), but after switching to the non-default printer driver (LJ), the issue disappeared.
I use the driver distributed by Canon (Canon MP620 serie). This issue happens only with Firefox 3.
I've downloaded Firefox 2 right now and tried reproducing this issue using exactly the same steps, the problem doesn't happen.
With Safari or Camino this problem doesn't happen either.
yes, this is caused by your printer driver. please file a bug w/ canon
Assignee: nobody → giles.puckett
Component: General → Printing: Setup
Product: Firefox → Core
QA Contact: general → printing.setup
Summary: Second print attempt crashes firefox 3.0 [@ libobjc.A.dylib@0x15688 ] → Second print attempt crashes firefox 3.0 [@ libobjc.A.dylib@0x15688 - CanonIJPDE@0x1531e]
Version: 3.0 Branch → 1.9.0 Branch
Oh hold on, I find this response a bit easy.
How do you explain that with Firefox 2 this issue doesn't happen ?
Please clarify, thanks.
i don't have to. we have thousands of users, with hundreds of printer drivers, and only one set of printer drivers for which there's a problem. it's canon's job to tell me why they believe their code (for which i don't have source) is not broken and help me debug why my code is doing something wrong.

because their code isn't open, and because their code is the module that's crashing, we can't do anything to debug it.

as for why things changed, we've significantly rewritten large portions of our product which basically means we've changed how we call other things. it's certainly possible that today we're triggering a bug in printer drivers (and this happens often enough) whereas yesterday we didn't.

alternatively. if you want to write a replacement printer driver and prove to me that we're doing something wrong, you're free to do that, it'd be quite helpful, however, i don't expect you to do that.
I contacted Canon yesterday and they called me back to have all the details in order to progress the investigation and narrow down on the printer driver side.
They will keep me informed.

Beside that, I've seen that this bug has been reassigned to giles.puckett@cisra.canon.com.au. Is it a person working for Canon ?

Thanks for your assistance
point them to https://bugzilla.mozilla.org/show_bug.cgi?id=441350#c14 and explain that if they have questions this system is open, they can create an account and ask here.

the person to whom i've assigned this bug is merely someone w/ an address that resembles canon, and who has used bugzilla at some point in the past, it is not indicative that this person still works for canon or would be able to find someone who would know someone who could help. it depends on the company, in some cases this works well, and in some cases, nothing happens, otoh, short of me making a phone call (which I have done in a number of cases), it's the best I can do.
(In reply to comment #24)
> I contacted Canon yesterday and they called me back to have all the details in
> order to progress the investigation and narrow down on the printer driver side.
> They will keep me informed.
> 

did you get any more information from Canon yet?  Having same problem here.
If this is the same issue as Bug 460963 (stack seems indentical but symptoms slightly different), there seem to be some individuals in that bug who have had success with the new printer driver on the Canon site.
This doesn't seem to be just a Canon issue.  I get this when I try to print to my wife's HP PhotoSmart over the network as well.  Print Preview and Print PDF do it, too.  Like Nicholas Wipfli, I don't have this problem with Safari or Camino.  I've also given up on Firefox because of this and now strictly use Camino.  It doesn't have as many features but it runs faster and hasn't crashed on me.
ttenley: you want bug 396680, not this one.

and i respectfully request that you respect everyone who uses our bug system by actually reading and thinking about the comments in bugs before you add your own. there is enough information here to indicate to you that you need to use a different bug if your printer driver is from a different vendor.
Timeless and others:

I apologize if anything I've posted here was disrespectful.  That was certainly not my intent.  My primary printer is a Canon printer, which is the printer I was using when I first experienced the crash.  I have subscribed and voted for this bug because when I found it it seemed to best fit the problem I've been experiencing.  I posted the comment about also being a problem with the HP printer thinking it would be helpful to know this is not just a problem with Canon printers.

Thank you for pointing out bug 396680.  I will review that bug and if it seems to better describe the problem I am having I will remove my vote from this bug and add myself to the CC list on 396680.

Again, I apologize for any breach of etiquette.
Assignee: giles.puckett → nobody
Maybe it helps to report my experiences/problems with FF 3.x (crashs while printing more than one time). They are the same, in all 3.x versions.
 
I'm using an Intel-Mac, (OS 10.5.7), and a Canon Printer (i 4600) and driver. The bug can easily be reproduced. I hoped it didn't with FF 3.5 but it did.

What dizzles me (cf. #22) as well is that Safari doesn't crash when printing a second time in a session. So it will be apparently no single or accidental event.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → DUPLICATE
Crash Signature: [@ libobjc.A.dylib@0x15688 - CanonIJPDE@0x1531e]
You need to log in before you can comment on or make changes to this bug.