On 2020-05-19 07:55, Samuel Sieb wrote:
Ok, then it could still be the regular oom killer. You would have to keep an eye on the
memory levels to see if there's a correlation with the tabs going away.
I have an up-to-date Firefox on F31 and I've recently had the entire browser crash a
couple of times. I have significant swap usage, but it appeared to be a crash, not a
memory kill.
One can always check the journal.
The entries as a result of doing "tail /dev/zero" and no earlyoom running, just
oom_reaper were
May 19 12:39:35
f32k.greshko.com kernel: tail invoked oom-killer:
gfp_mask=0x100dca(GFP_HIGHUSER_MOVABLE|__GFP_ZERO), order=0, oom_score_adj=0
May 19 12:39:36
f32k.greshko.com kernel: oom_kill_process.cold+0xb/0x10
May 19 12:39:36
f32k.greshko.com kernel: [ pid ] uid tgid total_vm rss
pgtables_bytes swapents oom_score_adj name
May 19 12:39:36
f32k.greshko.com kernel:
oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1026.slice/session-2.scope,task=tail,pid=974,uid=1026
May 19 12:39:36
f32k.greshko.com kernel: Out of memory: Killed process 974 (tail)
total-vm:3611260kB, anon-rss:960900kB, file-rss:128kB, shmem-rss:0kB, UID:1026
pgtables:6712kB oom_score_adj:0
May 19 12:39:36
f32k.greshko.com kernel: oom_reaper: reaped process 974 (tail), now
anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
--
The key to getting good answers is to ask good questions.