201894 - TalkBack doesn't report some Mozilla and Camino crashes on Mac OS X

Status: RESOLVED INVALID

(Core Graveyard :: Talkback Client, defect)

Description

[Greg K.]

TalkBack for Mac OS X doesn't report some Mozilla crashes. Crash bugs that
report crashes TalkBack doesn't report should block this bug.

Comment 1

[Greg K.]

Adding dependency on crash bugs that explicitly mention that TalkBack doesn't run.

Comment 2

[Ben Slade]

I think I've noticed Apple's crash reporter tool running instead of talkback
when Moz crashes Apple's crash reporter tool also runs when other non-Moz
applications crash.   This was on OS X 10.3.2.  I'm on 10.3.3 now.  I'll see if
I can recreate the scenario.

Comment 3

[Ben Slade]

Well, I was able to recreate the "no Mozilla talkback after a crash" problem on
OS X 10.3.3 (with Moz 1.6).  Here's the first dialog box from Apple which asks,
"Would you like to submit a bug report to Apple?":

http://www.benslade.com/misc/NoMozTalkback/MozQuitBugReportToAppleQuestion.gif

Here's the next form which comes up containing the crash information and asking
for user input on what was happening when it crashed:

http://www.benslade.com/misc/NoMozTalkback/AppleCrashReportForm.gif

The full text of the stack dump (if anybody happens to be interested), is here:

http://www.benslade.com/misc/NoMozTalkback/MozFlashCrashAppleBugReport.txt

The help screen for Apple's Crash Reporter says:

"You can view crash logs in Console, located in Applications/Utilities. In the
Logs list, user application crashes are located in ~/Library/Logs/CrashReporter
and system application crashes are located in /Library/Logs/CrashReporter."

So is Apple's Crash Reporter preempting Moz's Talkback feature?  Do the crash
reports to Apple ever get fed back to the Mozilla organization?

Comment 4

[Matthew Elvey]

If mozilla has hung, can one send a signal to it (e.g. kill -s one of 
 1) SIGHUP       2) SIGINT       3) SIGQUIT      4) SIGILL
 5) SIGTRAP      6) SIGABRT      7) SIGEMT       8) SIGFPE
 9) SIGKILL     10) SIGBUS      11) SIGSEGV     12) SIGSYS
13) SIGPIPE     14) SIGALRM     15) SIGTERM     16) SIGURG
17) SIGSTOP     18) SIGTSTP     19) SIGCONT     20) SIGCHLD
21) SIGTTIN     22) SIGTTOU     23) SIGIO       24) SIGXCPU
25) SIGXFSZ     26) SIGVTALRM   27) SIGPROF     28) SIGWINCH
29) SIGINFO     30) SIGUSR1     31) SIGUSR2 )
to get it to send a Talkback report?  There's a bug in new in 1.7 RCs that I'm
trying to nail down.

Comment 5

[Greg K.]

Matthew, you can use the Sampler application included in Apple's Developer Tools
to gain useful information about Mozilla hangs.

Comment 6

[Ben Slade]

I think this problem might be fixed.  

On my Mac, OS X 10.3.4 with Mozilla 1.7 [<i>Mozilla/5.0 (Macintosh; U; PPC Mac
OS X Mach-O; en-US; rv:1.7) Gecko/20040616</i>], when I force Mozilla to abort
using "kill -6" (after my email client hangs for other reasons), I now get the
Mozilla Talkback related prompts (ie. instead of Apple's Crash Reporter program
taking over)

Comment 7

[Ben Slade]

Actually, some more experience (after the previous comment) shows that
<i>both</i> Mozilla's Talkback program <i>and</i> Apple's Crash Reporter program
run after a crash.  

I've seen this behavior with an email related crash (attempting to exit with a
hung IMAP connection), and with a Java applet related crash (hitting the "back"
button before the applet finishes loading).

Comment 8

[Wayne Mery (:wsmwk)]

last blocking bug is to be kclosed, and talkback is obsolute/obsolete :)
=> invalid (meta)