On Wed, 2022-01-12 at 08:40 -0500, Robert Moskowitz wrote:
On 1/12/22 06:09, Patrick O'Callaghan wrote:
> On Wed, 2022-01-12 at 20:25 +1030, Tim via users wrote:
> > On Tue, 2022-01-11 at 16:58 -0500, Robert Moskowitz wrote:
> > > what is 'earlyoom'?
> > OOM is an out-of-memory condition, earlyoom is something that's
> > supposed to jump in and manage the memory use (somehow) before
> > you
> > run
> > out of free memory.
> >
> > I'm not surprised at Firefox being a problem. It's a behemoth of
> > a
> > program, all feature-full web browsers are, and there's a lot of
> > bad
> > websites (intentional or not).
> >
> > Just the other day I spent over an hour pruning all the tabs I'd
> > left
> > open of things I had/hadn't finished researching over the last
> > year.
> > There was a lot of, close tab I've read that, close the tab
> > because
> > the
> > site has vanished (always download anything you consider vital),
> > and
> > bookmark it for later and close the tab.
> You might consider the Tab Session Manager extension. It
> periodically
> (or on demand) saves your current tabs and windows and can restore
> them
> again on startup, but optionally not actually load each page until
> you
> decide to visit it.
I seem to get that behavior now out of the box with Ff 95 in Fed35?
Just yesterday, to clean memory up, I <cntl-q> firefox. Waited a
while
until top reported all those "Isolated web" processes ended,
restarted
Firefox, and all my windows and tabs restored. The tabs were there,
but
no 'content' until I switched to said tab and THEN the content was
received.
I used to rely on this behaviour, but it frequently didn't work
properly. I don't know if it's because I use KDE rather than Gnome, but
the extension has proved more reliable though still not perfect.
poc