> I think you have a problem there too.
oh I'm certainly not claiming a 1g default swap is appropriate, that
does seem far, far too small to me and will likely cause widespread
issues beyond just this, I was only saying that tweaking the systemd-
oomd swap % full setting would IMHO not be likely t
Well funny you should say that... When I installed 22.04 on my new Dell
laptop with 16G RAM, Jammy still only allocated 976MB of swap. I think
you have a problem there too.
So after reporting this issue and continually having OOM crashes, I
created a 20G swapfile - and ever since this problem has
> it's going to be hard to get around the core issue of oomd counting
pagecache as memory pressure
assuming my quick 10-minute assessment of this bug is correct, of
course...maybe i'm totally wrong about what the problem is ;-)
--
You received this bug notification because you are a member of Ub
> So, maybe the default SwapUsedLimit is not appropriate for Ubuntu
I don't think tweaking that will help much if at all, it's going to be
hard to get around the core issue of oomd counting pagecache as memory
pressure
--
You received this bug notification because you are a member of Ubuntu
Touc
In the near term, we could consider tweaking the systemd-oomd defaults
in Ubuntu. According to the commit that added systemd-oomd in Jammy [1],
the current config is based on Fedora's. This includes using the default
value of SwapUsedLimit=90% [2]. However, Fedora has more swap space by
default: a
wow, looking at the systemd code (even upstream), oomd is counting
pagecache as 'used' memory which is massively unfair as the kernel is
responsible for pagecache use, not userspace, and it's not even accurate
(from a OOM perspective) since the kernel will drop pagecache as memory
pressure increase
** Also affects: systemd (Ubuntu Jammy)
Importance: High
Status: New
** Tags removed: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966381
Title
** Tags added: fr-2157
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966381
Title:
applications crash that never crashed under Ubuntu-20.04
Status in systemd package in
Oh well, that latest systemd-oom didn't help. Chrome just crashed again
- while I wasn't even using the computer. Here are all the syslogs at
the time it crashed - nothing but the OOM
Mar 28 19:30:56 ubuntu systemd-oomd[1121]: Killed
/user.slice/user-1001.slice/user@1001.service/app.slice/app-gno
FYI About 6 hours ago I saw a new release of systemd-oom was released
(249.11-0ubuntu2). I've upgraded the entire system and rebooted, so I'll
report back if there's any change. I was getting these random OOM about
every couple of days, so within a week should know if that changed
anything
--
You
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966381
Title:
applications crash that never crashed under
Thank you for the report, tagging as rls incoming because it sounds like
we should ensure the systemd-oomd behaviour is what is expected or if
it's maybe kicking in more early than it should
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Ubuntu
T
12 matches
Mail list logo