Re: Figure out what killed an app (rhbz#2253099)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2024-01-31 at 13:40 -0500, Paul Grosu wrote:
> 2) Or you can completely disable it:

	Hi,
I do not want to disable the oom service. Remember, it does that on
user machines, not only on mine. Telling people: "you want to use app
a, b, c, then disable oom" as a new Fedora 40 feature is not great ;)

Nonetheless, I though I'll give it a try and will trigger the oom, to
see what it does. I wrote a little app to allocate gigabytes of memory
(until malloc() returns NULL) and one process was not enough, thus I
ran second and then third and then I've been notified by a gnome-shell
bubble telling me "Virtual Terminal Stopped" with a reason that memory
is almost full. Looking on the terminals the second process I ran had
been killed and the `dmesg` shows a reason:

[ 1712.960372] oom-
kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0
,global_oom,task_memcg=/user.slice/user-1000.slice/user@1000.service/ap
p.slice/app-org.gnome.Terminal.slice/vte-spawn-7f4b1469-38d1-498f-b363-
1c8311d2fcff.scope,task=alloc-too-much,pid=3323,uid=1000

[ 1712.960389] Out of memory: Killed process 3323 (alloc-too-much)
total-vm:137300925912kB, anon-rss:128kB, file-rss:1280kB, shmem-
rss:0kB, UID:1000 pgtables:1544608kB oom_score_adj:200

The journal contains similar information, plus a lot of debugging
information from kernel, starting with:

Feb 01 08:45:47 localhost.localdomain kernel: alloc-too-much invoked
oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP),
order=0,.......

The kernel tracing log for sig==9 shows:

gnome-terminal--2924    [002] dN.2.  2520.462889: signal_generate:
sig=9 errno=0 code=128 comm=alloc-too-much pid=3502 grp=1 res=0

There is no such thing (apart of the tracing log) when Evolution is
suddenly killed, the logs are muted. That makes me believe it's not the
OOM killer whom kills the application. I'm back at square 1; or maybe
square 2, as I know possibly kernel sends it, but not why.

	Bye,
	Milan
--
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux