On 04/04/2020 15.39, Carlos E. R. wrote:
On 04/04/2020 15.28, Carlos E.R. wrote:
On 04/04/2020 14.58, Per Jessen wrote:
Carlos E.R. wrote:
"glib-error ** creating thread 'main' error creating thread resource temporarily unavailable"
https://bugzilla.redhat.com/show_bug.cgi?id=995177
Last comment says:
Just FYI, I hit the same traceback after hitting the user limit on number of processes (ulimit -u), which is 1024 by default. I had firefox with ~700 threads. Raising it to 4096 fixes the issue for me.
I remember now that I changed firefox performance settings, first to "auto", then to "8" processes. It was set to 4.
Just rebooted:
cer@Telcontar:~> ps -eLf | grep firefox | wc -l 456 cer@Telcontar:~>
I have:
Telcontar:~ # ulimit -u 1850 cer@Telcontar:~> ulimit -u 1200 cer@Telcontar:~>
Now:
cer@Telcontar:~> ulimit -u 4096
Telcontar:~ # ulimit -u 2000
We'll see what happens.
I hibernated for siesta, restored, and it is working. I just opened a dozen youtube tabs, no issues. So the hypothesis now is that firefox with performance setting, process limit set to 8, opens so many threads that the system was starving. cer@Telcontar:~> ps -eLf | grep firefox | wc -l 460 cer@Telcontar:~> And I had two firefox openened (different profiles). With both running, I get: cer@Telcontar:~> ps -eLf | grep firefox | wc -l 866 cer@Telcontar:~> And the limit was 1200. What I don't know is how to find out how many are used, say now. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)