Re: firefox eats threads

[David Brownlee <abs%absd.org@localhost>]

On 18 March 2015 at 13:26, Thomas Klausner <wiz%netbsd.org@localhost> wrote:
> Hi!
>
> Over the last months I have noticed a pattern. When I leave a firefox
> process running for some time, it reduces the available threads for
> other programs. The symptom is that other programs (like git, gnucash,
> or anything that needs threads) don't start or have weird failure
> modes.
>
> When I quit and restart firefox, there are immediately enough threads
> available again. So I'm sure it's firefox-related.
>
> Last night I noticed that this even happens when I'm not actively
> doing anything in it (so perhaps extensions or firefox sync also have
> an influence).
>
> Did anyone else notice this?

Yes - sometimes if I have enough other threads consumed Firefox will
not even start. It *might* be increased by various plugins.

I suspect that 160 threads is just not enough for a "modern" desktop machine.

On my laptop I ended up setting rlimit.maxlwp.soft to 2048 and
maxprox/descriptors to 8192 a while back to avoid having to fight with
this....