3 ms·
Reading the bug report: 1. Increasing htop's refresh rate (-d 0.1), and having a tight loop that spawns processes quickly, tends to reproduce fairly reliably.
by RJIb8RBYxzAMX9u 9y ago
Reading the bug report:
1. Increasing htop's refresh rate (-d 0.1), and having a tight loop that spawns processes quickly, tends to reproduce fairly reliably.
2. Running htop as root seems to work around the problem.
I was able to reproduce the crash with (1), and not able to with (2) after running htop for several minutes. My first thought was that it didn't have to with running htop as root, but rather running htop as a different user as the one spawning processes. So I repeated (1) except that I ran htop as myself, but the spawning loop as nobody, and the crash went away.
I wonder if the bug's in the resource limit checks (RLIMIT_NOFILE, RLIMIT_NPROC), and if increasing the limits would delay / mitigate the crash. But I don't feel like crashing my machine anymore tonight to find out...
- gargravarr 9y agoSome nice digging there, thanks for the info!