This may be slightly OT. If so, apologies.
I find that Firefox tends to slow down and consume more memory over time, presumably because some tab is doing a lot of work. However the usual process listings from 'top' or 'glances' just show a bunch of fairly cryptic threads such as:
85.4 20.3 7.12G 3.11G 2704 poc 2h55:08 45 0 R 391K 0 /usr/lib64/firefox/firefox -contentproc -childID 5 -isForBrowser -prefsLen 291 -prefMapSize 29096 ... and so on, so it's hard to know which one is associated with which tab (or tabs).
Does anyone have a cheat sheet to help in pinning down the culprit(s)?
poc
On Fri, Jan 29, 2021 at 11:06:57AM +0000, Patrick O'Callaghan wrote:
I find that Firefox tends to slow down and consume more memory over time, presumably because some tab is doing a lot of work. However the usual process listings from 'top' or 'glances' just show a bunch of fairly cryptic threads such as:
85.4 20.3 7.12G 3.11G 2704 poc 2h55:08 45 0 R 391K 0 /usr/lib64/firefox/firefox -contentproc -childID 5 -isForBrowser -prefsLen 291 -prefMapSize 29096 ... and so on, so it's hard to know which one is associated with which tab (or tabs).
Does anyone have a cheat sheet to help in pinning down the culprit(s)?
There's a weirdly-well kept secret — Firefox has its own built-in "top"! Check this out:
about:performance
in the firefox toolbar.
On Fri, 29 Jan 2021 09:27:18 -0500 Matthew Miller mattdm@fedoraproject.org wrote:
On Fri, Jan 29, 2021 at 11:06:57AM +0000, Patrick O'Callaghan wrote:
it's hard to know which one is associated with which tab (or tabs).
Does anyone have a cheat sheet to help in pinning down the culprit(s)?
There's a weirdly-well kept secret — Firefox has its own built-in "top"! Check this out:
about:performance
in the firefox toolbar.
Whoa! All this time and I didn't know about that. Thanks.
On Fri, 2021-01-29 at 09:27 -0500, Matthew Miller wrote:
On Fri, Jan 29, 2021 at 11:06:57AM +0000, Patrick O'Callaghan wrote:
I find that Firefox tends to slow down and consume more memory over time, presumably because some tab is doing a lot of work. However the usual process listings from 'top' or 'glances' just show a bunch of fairly cryptic threads such as:
85.4 20.3 7.12G 3.11G 2704 poc 2h55:08 45 0 R 391K 0 /usr/lib64/firefox/firefox -contentproc -childID 5 -isForBrowser -prefsLen 291 -prefMapSize 29096 ... and so on, so it's hard to know which one is associated with which tab (or tabs).
Does anyone have a cheat sheet to help in pinning down the culprit(s)?
There's a weirdly-well kept secret — Firefox has its own built-in "top"! Check this out:
about:performance
in the firefox toolbar.
Amazing. Thanks :-)
poc
me too,thx!!
On Fri, Jan 29, 2021 at 8:10 AM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Fri, 2021-01-29 at 09:27 -0500, Matthew Miller wrote:
On Fri, Jan 29, 2021 at 11:06:57AM +0000, Patrick O'Callaghan wrote:
I find that Firefox tends to slow down and consume more memory over time, presumably because some tab is doing a lot of work. However the usual process listings from 'top' or 'glances' just show a bunch of fairly cryptic threads such as:
85.4 20.3 7.12G 3.11G 2704 poc 2h55:08 45 0 R 391K 0
/usr/lib64/firefox/firefox -contentproc -childID 5 -isForBrowser -prefsLen 291 -prefMapSize 29096
... and so on, so it's hard to know which one is associated with which tab
(or tabs).
Does anyone have a cheat sheet to help in pinning down the culprit(s)?
There's a weirdly-well kept secret — Firefox has its own built-in "top"! Check this out:
about:performance
in the firefox toolbar.
Amazing. Thanks :-)
poc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 1/29/21 6:27 AM, Matthew Miller wrote:
On Fri, Jan 29, 2021 at 11:06:57AM +0000, Patrick O'Callaghan wrote:
I find that Firefox tends to slow down and consume more memory over time, presumably because some tab is doing a lot of work. However the usual process listings from 'top' or 'glances' just show a bunch of fairly cryptic threads such as:
85.4 20.3 7.12G 3.11G 2704 poc 2h55:08 45 0 R 391K 0 /usr/lib64/firefox/firefox -contentproc -childID 5 -isForBrowser -prefsLen 291 -prefMapSize 29096 ... and so on, so it's hard to know which one is associated with which tab (or tabs).
Does anyone have a cheat sheet to help in pinning down the culprit(s)?
There's a weirdly-well kept secret — Firefox has its own built-in "top"! Check this out:
about:performance
in the firefox toolbar.
That is a very well-kept secret. My usual method is to kill the process and see which tabs have the crash message on them. I expect I'll still have to do that, but at least I can find out exactly which tab in the group it was before I do.
On Fri, 2021-01-29 at 12:25 -0800, Samuel Sieb wrote:
On 1/29/21 6:27 AM, Matthew Miller wrote:
On Fri, Jan 29, 2021 at 11:06:57AM +0000, Patrick O'Callaghan wrote:
I find that Firefox tends to slow down and consume more memory over time, presumably because some tab is doing a lot of work. However the usual process listings from 'top' or 'glances' just show a bunch of fairly cryptic threads such as:
85.4 20.3 7.12G 3.11G 2704 poc 2h55:08 45 0 R 391K 0 /usr/lib64/firefox/firefox -contentproc -childID 5 -isForBrowser -prefsLen 291 -prefMapSize 29096 ... and so on, so it's hard to know which one is associated with which tab (or tabs).
Does anyone have a cheat sheet to help in pinning down the culprit(s)?
There's a weirdly-well kept secret — Firefox has its own built-in "top"! Check this out:
about:performance
in the firefox toolbar.
That is a very well-kept secret. My usual method is to kill the process and see which tabs have the crash message on them. I expect I'll still have to do that, but at least I can find out exactly which tab in the group it was before I do.
Are we to assume that "Energy Impact" is proportional to CPU usage, or is there some magic formula behind it?
poc
On 30/01/2021 06:37, Patrick O'Callaghan wrote:
On Fri, 2021-01-29 at 12:25 -0800, Samuel Sieb wrote:
On 1/29/21 6:27 AM, Matthew Miller wrote:
On Fri, Jan 29, 2021 at 11:06:57AM +0000, Patrick O'Callaghan wrote:
I find that Firefox tends to slow down and consume more memory over time, presumably because some tab is doing a lot of work. However the usual process listings from 'top' or 'glances' just show a bunch of fairly cryptic threads such as:
85.4 20.3 7.12G 3.11G 2704 poc 2h55:08 45 0 R 391K 0 /usr/lib64/firefox/firefox -contentproc -childID 5 -isForBrowser -prefsLen 291 -prefMapSize 29096 ... and so on, so it's hard to know which one is associated with which tab (or tabs).
Does anyone have a cheat sheet to help in pinning down the culprit(s)?
There's a weirdly-well kept secret — Firefox has its own built-in "top"! Check this out:
about:performance
in the firefox toolbar.
That is a very well-kept secret. My usual method is to kill the process and see which tabs have the crash message on them. I expect I'll still have to do that, but at least I can find out exactly which tab in the group it was before I do.
Are we to assume that "Energy Impact" is proportional to CPU usage, or is there some magic formula behind it?
Does https://support.mozilla.org/en-US/kb/task-manager-tabs-or-extensions-are-slo...
With the following definition:
Energy Impact shows the processing power being used by the CPU. Tasks with a higher energy impact will drain your battery quicker and may slow down the performance of your system.
Help?
-
Ed Greshko -
Jack Craig -
Matthew Miller -
Patrick O'Callaghan -
Samuel Sieb -
stan