On Fri, 10 Jan 2025 06:27:48 -0600, o1bigtenor wrote in message
<CAPpdf58wRdvUsn_B5o9_SxaGpbcXGDBwW=R=RaY3aqjyxy-7aA@???>:

> On Thu, Jan 9, 2025 at 3:37 PM Joel Roth via Dng <dng@???>
> wrote:
> >
> > Marc Petit-Huguenin wrote:
> > > On 1/9/25 1:05 PM, Joel Roth via Dng wrote:
> > > > Hi List,
> > > >
> > > > I've been happy with FF, mainly due to there being a wide
> > > > variety of plugins for ad and tracker blocking and various
> > > > other purposes.
> > > >
> > > > One gripe is that as I open more tabs, FF begins to use all
> > > > of my CPU.
> > > >
> > > > Periodically I have to kill and restart it. That works okay,
> > > > but it seems like the type of manual fi-diddling I'd prefer to
> > > > avoid.
> > > >
> > > > I'd consider switching to another browser with a sufficient
> > > > plugin ecosystem.
> > > >
> > > > I've also thought of writing some utility to watch FF and
> > > > popup a window prompting "FF CPU high usage alert! Kill and
> > > > restart?"
> > > >
> > > > Do other people have this issue? How do you deal with it?
> > > >
> > > > Thanks!!
> > >
> > >
> > > The “about:processes” URL brings a page with the memory and CPU
> > > usage for each process. With that, it is easy to close and
> > > reopen the offending tab (which in 99% of the cases is LinkedIn).
> > >
> >
> > That will do it, thanks!!
> >
> I've found that if I park the browser on a "New Tab" (commonly used 2
> or 3 at either end of the page" that resource consumption
> most often also retreats. If it doesn't - - - well then I use the
> "about:processes" url to kill the offending tab(s).
>
> HTH

..me, I'm lazier, I just put a noose around their necks with
e.g. 'cputool -c 150 -l 19 -- nice -n 19 brave-browser &'.
There's also cpulimit, which I haven't used much, because
my nice nice cputool combination works so nicely. ;o)

--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.