seems this crash is related to a Canon Driver and Mac 10.5.x http://crash-stats.mozilla.com/report/list?product=Firefox&version=Firefox%3A3.5.3&query_search=signature&query_type=exact&query=&date=&range_value=1&range_unit=weeks&do_query=1&signature=objc_msgSend%20|%20CanonIJPDE%400x1531e a lot of comments mentioned that this happened during printing

dupe or related to bug 460963 ?

Have we reproduced this?

FWIW, a Canon printer driver also crashes on Windows: bug 517233.

do we have someone with this Printer in MV ?

(In reply to comment #1) > dupe or related to bug 460963 ? Yes. chofmann mentions offset 0x1531e in bug 460963 comment 42 (though it looks like the bug was originally filed about a crash at offset 0x14111).

(In reply to comment #5) > (In reply to comment #1) > > dupe or related to bug 460963 ? > > Yes. chofmann mentions offset 0x1531e in bug 460963 comment 42 (though it > looks like the bug was originally filed about a crash at offset 0x14111). so duping to bug 460693 ?

(In reply to comment #6) > (In reply to comment #5) > > (In reply to comment #1) > > > dupe or related to bug 460963 ? > > > > Yes. chofmann mentions offset 0x1531e in bug 460963 comment 42 (though it > > looks like the bug was originally filed about a crash at offset 0x14111). > > so duping to bug 460693 ? bug 460963 of course

Not clear why this was nominated as a 1.9.1 branch blocker. Do we think this is a problem in our code, or one we can mitigate? Rather than block we'll look at the fix after we have one since it will presumably block 1.9.2 as a topcrash

Not a blocker, though wanted. Kev: do we have contacts at Canon? This is getting increasingly strange. Josh: do we know why this would be a Firefox + driver problem? QA: can we buy one of these printers and get a trace in a debugger?

Mike: I have a Canon Printer down in the lab, and I have seen several Canon Pixma printers scattered about the office. I will investigate further with my 10.5 machines since it appears from the comment in the other bug that it was not happening on 10.6. (In reply to comment #9) > Not a blocker, though wanted. > > Kev: do we have contacts at Canon? This is getting increasingly strange. > Josh: do we know why this would be a Firefox + driver problem? > QA: can we buy one of these printers and get a trace in a debugger?

Is this "carbon print dialog from cocoa app makes world sad"? Are we going to land that Cocoa printing stuff on 1.9.2 after all? (Or maybe, as would have been wise, we did that before the beta!)

So far I have tried to reproduce this on an 10.5.8 Intel Mac running 3.5.4 and a PPC Mac using two different Canon printers - ip4300 and ip2600. In both cases I used old printer drivers and so far I have not been able to crash. I tried different variations of settings as well. I noticed in the list of crash reports that they all seem to be 3.5.3, so I will revert to that version and report back.

No crash using Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 and printing to the Canon IP4300.

The Cocoa print dialog (bug 520494) has landed between Beta 1 and 2, but Beta 3 is still showing this crash: http://crash-stats.mozilla.com/report/list?product=Firefox&version=Firefox%3A3.6b3&query_search=signature&query_type=exact&query=objc_msgSend%20|%20CanonIJPDE%400x1531e&date=&range_value=1&range_unit=weeks&do_query=1&signature=objc_msgSend%20|%20CanonIJPDE%400x1531e

This bug might be a dup of bug 525277, which is fixed (in current Minefield nighlies) by my patch for bug 396680. If any of you can still reproduce this bug's crash in a current FF 3.6 beta or nightly, please also try a current Minefield (trunk, mozilla-central) nightly. Let us know your results.

http://crash-stats.mozilla.com shows that these crashes all happen on OS X 10.5.X.

This should be fixed by my patch for bug 396680, which has been on the trunk for a while, and just landed on the 1.9.2 and 1.9.1 branches.

QA cannot verify this fix since we cannot get the initial crash to occur. We'll have to see how the crash stats look post-release to see if the problem was addressed for the users seeing it.

These crashes are completely gone from FF 3.6.2 and 3.6.3.