Normally a user can have around 1200 threads running.
djviking@machine:~> ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 128285 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 1200 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
One should think this is enough.
I started to get problem starting applications, because the number of threads running on my system has gone to the roof.
Still after closing all my applications, there are roughly over 700 threads active.
Starting Vivaldi increases the number of threads to around 1000, Starting Chromium increase to 1200 threads.
I could increase the max user processes to 1850 (the same amount that root gets). I have done this on my work computer, but it seems like a workaround. Instead I would really like to address why there are so many threads, when I have no applications running.
top - 21:04:03 up 23 days, 22:41, 9 users, load average: 1,53, 1,71, 1,70 Threads:** 1208 **total,** 1 **running,** 1205 **sleeping,** 0 **stopped,** 2 **zombie %Cpu(s):** 3,2 **us,** 1,6 **sy,** 0,0 **ni,** 95,2 **id,** 0,0 **wa,** 0,0 **hi,** 0,0 **si,** 0,0 **st KiB Mem: ** 32863936 **total,** 24904764 **used,** 7959172 **free,** 607484 **buffers KiB Swap:** 0 **total,** 0 **used,** 0 **free.** 15635464 **cached Mem