But what if the OOM notification daemon gets killed by the OOM killer?
You can't fool me, they have another daemon for that
It doesnt. Instead daemon terminates whole Linux
The OOM killer always, invariably starts off with killing the display server. Any side effects such as "the notification daemon loses its connection and closes" or "every single thing that you were working on loses its connection and closes" is incidental.
i will never stop wanting to commit severe crime every time i try to see what's using the processor and every single fucking system monitor tool just says it's xorg
But what if the OOM notification daemon gets killed by the OOM killer?
You can't fool me, they have another daemon for that
It doesnt. Instead daemon terminates whole Linux
The OOM killer always, invariably starts off with killing the display server. Any side effects such as "the notification daemon loses its connection and closes" or "every single thing that you were working on loses its connection and closes" is incidental.
i will never stop wanting to commit severe crime every time i try to see what's using the processor and every single fucking system monitor tool just says it's xorg
YES THANK YOU VERY USEFUL GOOD