cracauer@
Developer
I don't know anymore why it is a question why you use FreeBSD.
Systemd and Ubuntu are really more than the sum of their parts. In a bad way.
Out-of-memory kill. OK.
Don't think that `dmesg` has any information about the OOM situation, or even that one happened in the first place. Mind you, `dmesg` is clogged up with all kinds of garbage from systemd that doesn't belong there, starting with lots of error messages from the snap mechanism. I have no snaps installed. And the installation is less than 24 hours old, why is snap already spewing error messages?
/var/log/syslog has the OOM info. It also tells you that systemd has Taken Over(tm) the duties of picking the processes to kill. Note plural, it killed a whole group, although only one of them was big. And worst of all, it killed the (small) tmux process around the failed build. So I can't see how far it made it and which part blew up memory. I don't recall the old in-kernel OOM killer being this stupid.
Systemd and Ubuntu are really more than the sum of their parts. In a bad way.
Out-of-memory kill. OK.
Don't think that `dmesg` has any information about the OOM situation, or even that one happened in the first place. Mind you, `dmesg` is clogged up with all kinds of garbage from systemd that doesn't belong there, starting with lots of error messages from the snap mechanism. I have no snaps installed. And the installation is less than 24 hours old, why is snap already spewing error messages?
/var/log/syslog has the OOM info. It also tells you that systemd has Taken Over(tm) the duties of picking the processes to kill. Note plural, it killed a whole group, although only one of them was big. And worst of all, it killed the (small) tmux process around the failed build. So I can't see how far it made it and which part blew up memory. I don't recall the old in-kernel OOM killer being this stupid.