SIGKILL is almost always sent by systemd-oomd (or the kernel OOM
killer). That's the most likely explanation. Theoretically it could
also be sent by systemd if a service didn't quit quickly enough
following a SIGTERM. Maybe it could also be sent by mutter if a program
is unresponsive?
WebKitGTK doesn't use SIGKILL to clean up after itself. The parent
process just closes its IPC socket to the child process, then the child
should either (a) exit normally, or (b) crash itself, if its watchdog
thread detects the main thread has hung.
On Wed, Jan 31 2024 at 11:08:16 AM +01:00:00, Milan Crha
<mcrha@xxxxxxxxxx> wrote:
Jan 31 10:49:23 localhost.localdomain xdg-desktop-por[2697]: Realtime
error: Could not map pid: Could not determine pid namespace: Could not
find instance-id in process's /.flatpak-info
This one is https://bugs.webkit.org/show_bug.cgi?id=238403 (fixed
recently)
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
