On 12/2/23 20:58, jeremy ardley wrote:
I noticed my Firefox -esr browser becoming progressively more
sluggish. Then suddenly I was back to the system login screen
This is not the first time this has happened although previously
when it started getting sluggish I killed all Firefox related
process
System logs show the start of the event.
2023-12-03T11:35:03.335043+08:00 client kernel: [3792101.257070]
Isolated Web Co invoked oom-killer:
gfp_mask=0x140dca(GFP_HIGHUSER_MOVABLE|__GFP_COMP|__GFP_ZERO),
order=0, oom_score_adj=100<snip>
On 12/2/23 22:33, jeremy ardley wrote:
On 3/12/23 13:59, Phil Wyett wrote:
Your system RAM total is?
32G
You have swap and it is enabled?
No Swap. I prefer not on SSD
What Desktop Environment (DE) are you using - GNOME, KDE etc.?
Mate with multiple panels.
How many apps would you normally be running on the system at once?
3 x web browsers Firefox - multiple windows, Chrome one window,
Chromium one window
Intermittently mate terminals and LibreOffice applications
How many extensions have you installed/running in firefox?
Several. All the usual blockers plus bypass paywalls clean and Multi
Account Containers
How many tabs would you normally have open?
In firefox, perhaps 20 over two windows
What type of content is generally being viewed/used in firefox?
A lot of video and otherwise news and search and GPT4
When the system starts to become sluggish, have you looked at the
firefox 'Task Manager' under tools to see if anything stands out?
Previously I have seen the Isolated Web Co processes maxing CPU and
the CPU fans starting to roar. Nothing unusual in content at the
time and if I kill all ESR related processes it quiets down and I
can resume the closed windows and tabs at much reduced CPU
It's obvious the main culprit is Firefox-ESR and the Isolated Web Co
processes. What triggers it other than elapsed time I have no idea
On 12/2/23 22:59, jeremy ardley wrote:
I don't think it is actually a lack of memory. What I do see is all
the web browsers are up there on CPU along with nvidia-modeset.
Putting in swap may delay the time things start going awry but the
cause won't be lack of memory
I tried running a Debian desktop without swap and encountered the same
symptom -- crashed desktop and return to login screen. The solution was
two-fold:
1. Provision 1 GB of swap.
2. Add Xfce panel widgets so that I can see what is going on.
Between the two, I usually have enough time to kill problem apps before
a crash.
And, more memory would not hurt.
David
