On Sun, 15 Dec 2019 08:18:57 +0100 Wolfgang Rosenauer wrote:

Try about:performance ?

Wolfgang

Ooh, shiny! Thanks. :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun, 15 Dec 2019 18:19:55 -0500 ken wrote:

On 12/15/19 2:18 AM, Wolfgang Rosenauer wrote:

...

Hi,

Am 15.12.19 um 00:08 schrieb ken:

...

I have a couple Firefox windows open and with multiple tabs open in each window.  One of the webpages in one of those tabs is misbehaving, running the CPU up to 100% (and heating up this laptop).

I have determined which Firefox PID that is causing the problem, but how do I find out which Firefox tab corresponds to that PID? Running "ps -Fp [pidnum]" gives a lot of info, but not which window and tab, or the bad webpage's URL, or anything else helpful.

(Note: Yes, "kill [pidnum]" works, but I'd like to know the URL that is misbehaving.) Try about:performance ?

Wolfgang

Thanks.  That's a good step in the right direction.  But it shows stats on just four tabs-- fewer than half the number currently open. There's great info there, just not enough.

Danke++

It seemed to show all mine. Are all your tabs in one window? If not, is it possible that some belong to a different firefox instance? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 16/12/2019 13.02, Dave Howorth wrote:

...

On Sun, 15 Dec 2019 18:19:55 -0500 ken wrote:

...

...

On 12/15/19 2:18 AM, Wolfgang Rosenauer wrote:

...

...

...

Try about:performance ?

Wolfgang

Thanks.  That's a good step in the right direction.  But it shows stats on just four tabs-- fewer than half the number currently open. There's great info there, just not enough.

Danke++

...

It seemed to show all mine. Are all your tabs in one window? If not, is it possible that some belong to a different firefox instance?

The tabs have to be "active".

For example, if you reload FF, only one tab per window is active.

First, I had to close down FF that was giving me trouble... something was running my CPU way too much, near to locking up my entire system.  I closed about four or five tabs which weren't essential, then restarted FF.  So far no obvious problems.  But this sort of problem happens regularly, though more often it's the RAM which is eaten up, driving swap crazy, and slowing down my system that way.  So currently I'm looking at a a system which is behaving. The term "active" is too slippery for me, maybe for FF as well.  Looking at about:performance, I see entries for five web pages   One is for about:performance itself (useful to display its existence?!).  Another is for a web page in the same FF window as about:performance.  A third is for a web page open in the only tab existing in a different FF window, a window which has been minimized since I started FF.  The other two are entries listed are for two tabs in a totally different window.  Currently there are five other FF windows open, all but one of which are minimized.  All five windows have multiple tabs.  FF's about:performance lists none of them and none of any of their tabs.  I'm not seeing any commonality in the five entries listed by about:performance which distinguish them from all the other tabs in all the other windows. It's my experience that most of the webpages in the world run some javascript or similar.  And I highly suspect that's the cause of the problem: some bad code which is running up the CPU (but more often RAM).  Well, the problem might also originate from one of the add-ons I've installed... that may be worth a look the next time the problem comes up.  But intuition is telling me the problem is more in the particular webpage. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/16/19 12:09 PM, Patrick Shanahan wrote:

* ken [12-16-19 11:53]:

...

...

On 16/12/2019 13.02, Dave Howorth wrote:

...

On Sun, 15 Dec 2019 18:19:55 -0500 ken wrote:

...

On 12/15/19 2:18 AM, Wolfgang Rosenauer wrote:

...

...

...

Try about:performance ?

Wolfgang Thanks.  That's a good step in the right direction.  But it shows stats on just four tabs-- fewer than half the number currently open. There's great info there, just not enough.

Danke++ It seemed to show all mine. Are all your tabs in one window? If not, is it possible that some belong to a different firefox instance?

The tabs have to be "active".

For example, if you reload FF, only one tab per window is active.

First, I had to close down FF that was giving me trouble... something was running my CPU way too much, near to locking up my entire system.  I closed about four or five tabs which weren't essential, then restarted FF.  So far no obvious problems.  But this sort of problem happens regularly, though more often it's the RAM which is eaten up, driving swap crazy, and slowing down my system that way.  So currently I'm looking at a a system which is behaving.

The term "active" is too slippery for me, maybe for FF as well.  Looking at about:performance, I see entries for five web pages   One is for about:performance itself (useful to display its existence?!).  Another is for a web page in the same FF window as about:performance.  A third is for a web page open in the only tab existing in a different FF window, a window which has been minimized since I started FF.  The other two are entries listed are for two tabs in a totally different window. 

Currently there are five other FF windows open, all but one of which are minimized.  All five windows have multiple tabs.  FF's about:performance lists none of them and none of any of their tabs.  I'm not seeing any commonality in the five entries listed by about:performance which distinguish them from all the other tabs in all the other windows.

It's my experience that most of the webpages in the world run some javascript or similar.  And I highly suspect that's the cause of the problem: some bad code which is running up the CPU (but more often RAM).  Well, the problem might also originate from one of the add-ons I've installed... that may be worth a look the next time the problem comes up.  But intuition is telling me the problem is more in the particular webpage.

a handy script I employe:

#!/bin/bash

# Loop until all parameters are used up echo "USER PID %CPU %MEM VSZ RSS TTY STAT START TIME # COMMAND"

while [ "$1" != "" ]; do ps -A auf |grep -i $1 |grep -v grep|grep -v psfind shift # Shift all the parameters down by one done

then, psfind firefox | less -S

will display the firefox windows with cpu usage and pid

when you determine which is causing concern, kill that pid and look to see which window is no longer available and you will know where the problem is. You can dive deeper after gaining this knowledge

example with lines abreviated for better display:

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND paka 5141 10.1 4.3 5031336 1607188 ? Sl 11:14 5:19 \_/usr/li paka 5523 3.2 1.7 3254812 657428 ? Sl 11:14 1:41 | \_//u paka 5930 2.1 1.2 2952404 479500 ? Sl 11:14 1:06 | \_usr paka 5975 1.1 0.6 27800976 235660 ? Sl 11:14 0:36 | \_/us paka 6110 0.8 0.7 2647396 268752 ? Sl 11:14 0:27 | \_/us paka 6135 1.3 1.4 9461752 526216 ? Sl 11:14 0:43 | \_/us paka 6164 4.8 1.7 3152444 658248 ? Sl 11:14 2:32 | \_/us paka 6194 0.5 0.8 2602832 310440 ? Sl 11:14 0:16 | \_/us paka 6223 15.2 1.1 2845804 413608 ? Sl 11:14 7:56 | \_/us paka 6252 1.2 0.8 2646712 307252 ? Sl 11:14 0:38 | \_/us paka 7008 0.0 0.1 213080 39500 ? Sl 11:14 0:00 | \_usr lines 1-12/12 (END)

Cool script.  I use "top" to do about the same, except I configure it to display processes sorted by "MEM" (or alternately "CPU").  That way, the biggest hogs are shown at the top.  I can also watch if the amount of that resource used decreases or increases. I've used that to find the process to kill... and it works to bring the system back to normal speed.  But it's too hard to figure out which process it was that I killed-- here, which tab of which FF window is now gone.  Life is too complicated. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* ken [12-16-19 13:45]:

On 12/16/19 12:09 PM, Patrick Shanahan wrote:

...

* ken [12-16-19 11:53]:

...

...

On 16/12/2019 13.02, Dave Howorth wrote:

...

On Sun, 15 Dec 2019 18:19:55 -0500 ken wrote:

...

On 12/15/19 2:18 AM, Wolfgang Rosenauer wrote:

...

...

> Try about:performance ? > > > Wolfgang Thanks.  That's a good step in the right direction.  But it shows stats on just four tabs-- fewer than half the number currently open. There's great info there, just not enough.

Danke++ It seemed to show all mine. Are all your tabs in one window? If not, is it possible that some belong to a different firefox instance?

The tabs have to be "active".

For example, if you reload FF, only one tab per window is active.

First, I had to close down FF that was giving me trouble... something was running my CPU way too much, near to locking up my entire system.  I closed about four or five tabs which weren't essential, then restarted FF.  So far no obvious problems.  But this sort of problem happens regularly, though more often it's the RAM which is eaten up, driving swap crazy, and slowing down my system that way.  So currently I'm looking at a a system which is behaving.

The term "active" is too slippery for me, maybe for FF as well.  Looking at about:performance, I see entries for five web pages   One is for about:performance itself (useful to display its existence?!).  Another is for a web page in the same FF window as about:performance.  A third is for a web page open in the only tab existing in a different FF window, a window which has been minimized since I started FF.  The other two are entries listed are for two tabs in a totally different window. 

Currently there are five other FF windows open, all but one of which are minimized.  All five windows have multiple tabs.  FF's about:performance lists none of them and none of any of their tabs.  I'm not seeing any commonality in the five entries listed by about:performance which distinguish them from all the other tabs in all the other windows.

It's my experience that most of the webpages in the world run some javascript or similar.  And I highly suspect that's the cause of the problem: some bad code which is running up the CPU (but more often RAM).  Well, the problem might also originate from one of the add-ons I've installed... that may be worth a look the next time the problem comes up.  But intuition is telling me the problem is more in the particular webpage.

a handy script I employe:

#!/bin/bash

# Loop until all parameters are used up echo "USER PID %CPU %MEM VSZ RSS TTY STAT START TIME # COMMAND"

while [ "$1" != "" ]; do ps -A auf |grep -i $1 |grep -v grep|grep -v psfind shift # Shift all the parameters down by one done

then, psfind firefox | less -S

will display the firefox windows with cpu usage and pid

when you determine which is causing concern, kill that pid and look to see which window is no longer available and you will know where the problem is. You can dive deeper after gaining this knowledge

example with lines abreviated for better display:

USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND paka 5141 10.1 4.3 5031336 1607188 ? Sl 11:14 5:19 \_/usr/li paka 5523 3.2 1.7 3254812 657428 ? Sl 11:14 1:41 | \_//u paka 5930 2.1 1.2 2952404 479500 ? Sl 11:14 1:06 | \_usr paka 5975 1.1 0.6 27800976 235660 ? Sl 11:14 0:36 | \_/us paka 6110 0.8 0.7 2647396 268752 ? Sl 11:14 0:27 | \_/us paka 6135 1.3 1.4 9461752 526216 ? Sl 11:14 0:43 | \_/us paka 6164 4.8 1.7 3152444 658248 ? Sl 11:14 2:32 | \_/us paka 6194 0.5 0.8 2602832 310440 ? Sl 11:14 0:16 | \_/us paka 6223 15.2 1.1 2845804 413608 ? Sl 11:14 7:56 | \_/us paka 6252 1.2 0.8 2646712 307252 ? Sl 11:14 0:38 | \_/us paka 7008 0.0 0.1 213080 39500 ? Sl 11:14 0:00 | \_usr lines 1-12/12 (END)

Cool script.  I use "top" to do about the same, except I configure it to display processes sorted by "MEM" (or alternately "CPU").  That way, the biggest hogs are shown at the top.  I can also watch if the amount of that resource used decreases or increases.

I've used that to find the process to kill... and it works to bring the system back to normal speed.  But it's too hard to figure out which process it was that I killed-- here, which tab of which FF window is now gone.  Life is too complicated.

use your cell phone to photograph the firefox instances -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 16/12/2019 17.52, ken wrote:

...

On 16/12/2019 13.02, Dave Howorth wrote:

...

On Sun, 15 Dec 2019 18:19:55 -0500 ken <> wrote:

I mean that it is actually loaded. When you restart FF only one tab per window is actually loaded, the rest are blank till you click on them. I don't click any till actually needed. And now and then you have to purge and remove tabs, they are memory hogs. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 16/12/2019 15.41, ken wrote:

On 12/16/19 7:02 AM, Dave Howorth wrote:

# ps -e | grep firefox 30274 ? 01:31:42 firefox

Try "ps asx | grep firefox" instead. I get 17 entries, but I have two FF running this moment. Killing one I get 11 entries (7 windows). - -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXfebYQAKCRC1MxgcbY1H 1Vi7AJ4oh1xhUe0DSaCVlmzg/4TJDofXNACeLI7b7++bah+KeyapNyPl0uioaN0= =3rnE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

16.12.2019 20:24, ken пишет:

...

On 16/12/2019 15.41, ken wrote:

...

On 12/16/19 7:02 AM, Dave Howorth wrote:

...

# ps -e | grep firefox 30274 ?        01:31:42 firefox

Try "ps asx | grep firefox" instead. I get 17 entries, but I have two FF running this moment. Killing one I get 11 entries (7 windows).

I get:

# ps asx | grep firefox|wc -l 6

but one of those is grep grepping itself... so 5 of something (?).  I have 8 FF windows open and all but one of those have multiple tabs, ALL of which were opened with one mouse-click (of course bringing back a previous session).

AFAIK firefox does not start new process for each tab/window; it has limited number of content processes that serve all current requests. Here with FF 71 it stops at 10 total processes even tough I have much more windows/tabs opened. All opened windows/tabs are listed in about:preference as far as I can tell. Number of content processes is default (8 which is max). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org