3 ms·
> I’ve tried keeping ActivityMonitor open to see if I can spot any process that is consuming too much CPU or memory (the obvious suspect would be WindowServer),
by embedding-shape 9mo ago
> I’ve tried keeping ActivityMonitor open to see if I can spot any process that is consuming too much CPU or memory (the obvious suspect would be WindowServer), but everything looks normal until the crash happens, and there is only so much attention one can spare while, you know, doing productive stuff.
I had a Linux box that suddenly dies, with no logs indicating what. Turns out that there was some segmentation fault in a service, which killed the computer before it had a chance to write to logs or before the logs were written to disk, somehow, not sure exactly how.
Not until I started sending the logs out to my desktop computer as they happened, could I finally figure out what service was crashing it.
Now macOS is absolutely horrible for headless operations (ask me, just set up one yesterday for signing purposes and it's just... No comment.), but surely there must be some way of macOS to send logs somewhere else, maybe you could try that instead of trying to see it as it happens.