254867 - Mac Report filed on PC Bugzilla does not detect Forcequits

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Elton Jones]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

Another bug related to buttons becoming disabled can only be corrected by force
quitting Mozilla. Bugzilla Talkback agent does not detect nor report this means
of abort. So far noone has been able to validate this freeze condition regarding
buttons

Reproducible: Always
Steps to Reproduce:
forcequit command not captured by bugzilla

Comment 1

[Jo Hermans]

It's actually called 'Talkback', not Bugzilla. Bugzilla is this webbased system,
where you can file bugs.

And I think that Talkback can't catch this force-quit, because it's really a
"kill -9" signal (KILL) that is send here, which is indeed not caught by
Talkback. It's only catches SEGV, INT, etc ...

Comment 2

[Stephen Donner [:stephend] Not actively reading bugmail]

A force quit is a user-generated event.  Talkback only traps OS and
application-level program terminations.  Therefore, it will not detect hangs,
only crashes.

Comment 3

[Ben Slade]

First, may I suggest, change the summary of this bug to, "Talkback not invoked
for Mac "Force Quit" (kill -9)

Second, this problem is about Talkback not about the buttons referred to in a
separate bug.  Since this problem with Talkback is definitely confirmed, should
the status of this bug be changed from Unconfirmed to New?

Third, why wouldn't you want to invoke Talkback when "force quit/kill -9" occurs?

IMHO reporting hangs is just as important as reporting crashes.

Ben in DC

Comment 4

[Ben Slade]

Oh yeah, the way to invoke Talkback for a hung Mozilla program on Mac OS X is to
startup the Terminal application and run the command:

ps -aux | egrep -i 'mozilla|^user' | grep -v grep

Then take the number from the PID column of the output and run the command:

kill -6 <PID>

Where <PID> is replace by the number from the "ps" command output.

This will kill your Mozilla process in an unkind way (sending an ABRT
signal/software interrupt), invoking the Talkback utility.

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.