On my 88 thread server, `show_kthreads = true` breaks things

[wallentx]

I've loved procs since the moment I found it, and then when v0.14.0 released, it just stopped showing processes from my user on my server. I thought it was because I had a weird issue that resulted in my UID being 1001, and my GID being 1002, and procs wouldn't show any processes ran by my user.
I tried procs <process name>, and procs --or <pid>, and it'd only print the header.

I went diving into the code to try and see if there was some filtering happening that would be due to UID and GID not matching, and I couldn't find anything.

After years of this not working on my server, I just now found that the issue was due to show_kthreads = true being set by default, and I was using a config named ~/.config/procs/procs.conf rather than config.toml, so the defaults weren't being detected by default.

Anyway, with show_kthreads = true, it doesn't show any processes from my user. It lists up to about 508 processes from root, and a few systemd-* users, and then appears to be done. I'm not sure why, since I didn't see anything specifying an upper limit if processes that it can sort through.

[apage43]

Stopping after a fixed # of processes is probably the same fd limit issue in #766