Your message dated Sat, 5 Jan 2008 17:19:09 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Should we close it?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: wmtop
Version: 0.7-1
When wmtop is run to display the 3 memory-hogging processes(wmtop -m)
it will show mozilla-bin 3 times (probably the child-processes running
in the same memory-space).
This kinda defeats the purpose of wmtop since mozilla will be on top:)
A screenshot is attached.
I use Debian 2.3(woody), kernel 2.2.15(own build)
and libc6 2.1.3-10
Paul.
--- End Message ---
--- Begin Message ---
On Jan 5, 2008 5:07 PM, Justin Pryzby <[EMAIL PROTECTED]> wrote:
> On Sat, Jan 05, 2008 at 01:19:29PM +0100, Sandro Tosi wrote:
> > Hi all,
> > wmtop reads its information from /proc fs, so if subprocesses (instead
> > of using threads) are listed more times, they are in the list.
> >
> > I don't think I want to change this behaviour, mainly because so many
> > things have changed in the kernel area from the time of report to now,
> > and it could still be that different threads of the same application
> > are listed as different processes under /proc.
> >
> > Justin, do you think we can close this report (no submit answer in
> > about 1 year, unreproduc here, no needed fix from my POV)?
> I agree that you shouldn't try to combine processes with their
> children, at least not without intending to spend lots of effort on
> this (the user has to be able to define what kinds of processes should
> be combined).
>
> However I don't know much about threads so I'm not sure; you can run
> "ps -eLF" and see that processes threads have the same PID and
> different LWP ID, but only the single PID has an entry in /proc.
>
> It seems like it'll probably be okay if you close the bug.
That said, I'm closing this bug. Thank you (all) for the attention.
Regards,
Sandro
--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
--- End Message ---
