Lol. Thanks. I really don’t care. I’m running linux servers professionally since the late 90s, which means I have seen one or the other WTF. And systemd had quit some of them, especially flooding log files and race conditions. For example see https://github.com/systemd/systemd/issues/7293. That took more than 2 years to fix. And if people like to downvote my personal experience with it they are welcome to do so. I mean all I did was answering a question why one might use a systemd free distribution. Oh and for the downvoters: SYSTEMD IS MICROSOFTS ATTEMPT TO KILL LINUX! Poettering always was their agent. https://en.m.wikipedia.org/wiki/Lennart_Poettering 😉
Usually a sign of multiprocessing/multithreading going wrong, e.g. accessing the same resource without proper locks like opening the same logfile in different processes and trying to write simultaneously. Those errors can be triggered just by reformating the code (or obfuscating in this case), thus changing the runtime behaviour slightly. Hard to find, especially since they’re dependent on the speed/workload of the machine running the code.