[Bug 1013871] Re: Firefox trunk showing as RunProcess in top

Thu Jun 21 21:36:06 UTC 2012

Launchpad has imported 11 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=765158.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2012-06-15T08:30:53+00:00 Erdem444 wrote:

Nightly 012-06-12-03-05-27 (fine) :
http://img135.imageshack.us/img135/5378/fx0120612030527.png

Nightly 012-06-14-07-59-12 (buggy) :
http://img59.imageshack.us/img59/7572/fx0120614075912.png

This behavior exists since 2012-06-13-03-05-35 build
(2012-06-12-03-05-27 is fine).

1-) Thread name is different. I checked it via "top" on terminal as you can see.
2-) "top" command on terminal shows it fine but it's somehow reporting to KDE's system monitor wrong. See memory usage(shows 2.12 GB, i have 2 GB ram) is wrong but if i look at details(right click -> detailed mem information) it's right. Except that, CPU state is becoming "stopped/suspended" when firefox use %0 CPU.

What do you think ? Second issue might be related to KDE's system
monitor but it was fine until 2012-06-13-03-05-35 build.

Regards. . .

Reply at: https://bugs.launchpad.net/firefox/+bug/1013871/comments/0

------------------------------------------------------------------------
On 2012-06-15T08:41:46+00:00 Ttaubert wrote:

I experience the same and Firefox shows up as "Main Thread" or
"RunProcess" in the process list.

Reply at: https://bugs.launchpad.net/firefox/+bug/1013871/comments/1

------------------------------------------------------------------------
On 2012-06-15T10:49:11+00:00 JohnFlux wrote:

Hi.  I'm the ksysguard maintainer.

It would be great for the firefox guys to fix the name of the process.

But I also need to fix the memory problem, and will have a look.

Reply at: https://bugs.launchpad.net/firefox/+bug/1013871/comments/2

------------------------------------------------------------------------
On 2012-06-15T10:57:13+00:00 JohnFlux wrote:

I run the nightly build of firefox, and the process name appeared as
"RunProcess".  I could not reproduce the Memory problem though.

When you see the memory problem again, could you please do:

cat /proc/$(pidof firefox)/statm

And paste the output?  (Please also check that "pidof firefox" also
returns the same PID that System Activity is using)

Reply at: https://bugs.launchpad.net/firefox/+bug/1013871/comments/3

------------------------------------------------------------------------
On 2012-06-15T11:06:56+00:00 Erdem444 wrote:

[omer at arch ~]$ pidof firefox
1202
[omer at arch ~]$ cat /proc/$(pidof firefox)/statm
154494 43815 7586 23 0 84796 0

Screenshot :
http://img29.imageshack.us/img29/5089/pidfx.png

Reply at: https://bugs.launchpad.net/firefox/+bug/1013871/comments/4

------------------------------------------------------------------------
On 2012-06-15T11:08:37+00:00 Ttaubert wrote:

This issue is caused by bug 720778.

Reply at: https://bugs.launchpad.net/firefox/+bug/1013871/comments/5

------------------------------------------------------------------------
On 2012-06-15T11:23:54+00:00 JohnFlux wrote:

Can you plese do:

cat /proc/$(pidof firefox)/status

As well?  Thanks

Reply at: https://bugs.launchpad.net/firefox/+bug/1013871/comments/6

------------------------------------------------------------------------
On 2012-06-15T11:32:17+00:00 Erdem444 wrote:

http://pastie.org/4091819

Reply at: https://bugs.launchpad.net/firefox/+bug/1013871/comments/7

------------------------------------------------------------------------
On 2012-06-15T13:42:05+00:00 Honzab-moz wrote:

We probably just need to avoid call of PR_SetCurrentThreadName("Main
Thread") on the main thread and then fix the visual event tracer to
specially handle main thread's name.

I'll do this on Monday, however anyone feel free to make a patch for
this, but please drop a note you do so.  Thanks.

Reply at: https://bugs.launchpad.net/firefox/+bug/1013871/comments/8

------------------------------------------------------------------------
On 2012-06-15T15:40:40+00:00 JohnFlux wrote:

The ksysguard problem should be fixed:

http://commits.kde.org/kde-
workspace/169899ce558f54ad1f37e84c18817b05e90c2ba8

Reply at: https://bugs.launchpad.net/firefox/+bug/1013871/comments/9

------------------------------------------------------------------------
On 2012-06-19T17:42:11+00:00 Honzab-moz wrote:

Created attachment 634497
v1

- removed naming of the main thread
- visual event tracer explicitly uses Main Thread as name of the main thread
- added support for nameless threads in even tracer

Reply at: https://bugs.launchpad.net/firefox/+bug/1013871/comments/11

** Changed in: firefox
       Status: Unknown => In Progress

** Changed in: firefox
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Mozilla
Bugs, which is subscribed to Mozilla.
https://bugs.launchpad.net/bugs/1013871

Title:
  Firefox trunk showing as RunProcess in top

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1013871/+subscriptions