I think your options are two:

1) Write a plugin for the oom service to capture the state (and log it) before it kills the process.  Here's the source code to learn more about that:

https://github.com/facebookincubator/oomd/

2) Or you can completely disable it:

https://www.cjjackson.dev/posts/what-is-systemd-oomd-how-to-disable-it/

The man pages which other folks referred to is here (in case you want to tweak with configuring it):

https://man7.org/linux/man-pages/man8/systemd-oomd.service.8.html

Hope it helps,
~p

On Wed, Jan 31, 2024 at 1:04 PM Michael Catanzaro <mcatanzaro@redhat.com> wrote:
On Wed, Jan 31 2024 at 06:53:25 PM +01:00:00, Milan Crha
<mcrha@redhat.com> wrote:
> Evo itself doesn't use any seccomp or such, these things can be used
> by
> the WebKitGTK. A quick grep revealed:
>
> https://github.com/WebKit/WebKit/blob/main/Source/WebKit/UIProcess/Launcher/glib/ProcessLauncherGLib.cpp#L258
>
> but that code does not seem to be called at this time (or my debug
> code
> was wrong, it's possible).

That code is for terminating child processes. It's certainly not
supposed to terminate itself.

--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue