160406 - Mozilla should change process info to reflect its state

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, enhancement)

Description

[Mirek Hankus]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1b) Gecko/20020718
BuildID:    2002071911

Sometimes one of processes od Mozilla takes 100% CPU and there is no way
to find out what this process is doing. 
I would like to sugest changing process info so that running

ps -ax |grep mozilla-bin

on UNIX systems (Linux in my case) would show some additiona info. 
Sendmail, PostgreSQL behave exactly that way. Whan you enter

ps -ax |grep sendmail 

you can see something like that

 9170 ?        S      0:02 sendmail: accepting connections
26325 ?        S      0:00 sendmail: server mail.freeswan.org 
27056 ?        S      0:00 sendmail: startup with imail2.gazeta.pl

and you know what your sendmail is doing (without any additional
debugging tools).

Reproducible: Always
Steps to Reproduce:
1. run: px -ax |grep mozilla
2.
3.

Comment 1

[Boris Zbarsky [:bzbarsky]]

this would be nice.

Comment 2

[Andrew Schultz]

sendmail does this a variety of different ways (it's highly platform-dependent).
 see sendmail/conf.c and sendmail/conf.h in the sendmail sources.
On Linux, it clobbers the contents of argv.

Note that you would no longer be able to differentiate processes base on
commandline parameters like:

mozilla -P default
mozilla -P somebody_else

I don't know if you could get different threads to have different info there or
not (is sendmail multi-threaded, or does it just spawn multiple instances as
needed?)

Also, the main thread is generally the only one that does any work...

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420