Hi Terry, > I think that it simply ran out of memory after maxing out the CPU > cores for a minute or two.
I'm surprised a Linux machine is configured to shutdown on persistent high CPU or memory load. Rather, the kernel's out-of-memory killer will kick in and guess a process to kill to free memory. It sometimes nobbles the wrong horse. Perhaps it sent some vital process to the glue factory which initiated an orderly shutdown, but I doubt it. Could it be the graphics driver in the kernel which is running amok? Chromium will be making it work hard by compositing lots of pixel rectangles. https://superuser.com/questions/1716854/disabling-gpu-compositing-for-all-chrome-and-electron-instances-on-a-mac You might find some indication of past problems with ‘sudo -i journalctl’. It will place you in less(1). There's the date to go by and you can search with ‘/’, e.g. ‘oom-killer’. -- Cheers, Ralph. -- Next meeting: Online, Jitsi, Tuesday, 2023-12-05 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
