Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Learn More

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

[Linux][Flatpak] Firefox 177.0.1 spawns over 1000 threads of Web Content

  • 4 odgovora
  • 0 ima ovaj problem
  • 24 prikaza
  • Posljednji odgovor od Arda

Arda
Arda
more options

This happens at random intervals, mostly when firefox is being left idle.

Since it starts >1000 threads, it easily fills ram and swap, then get killed by OOM killer. Hence no crash reports.

I'll upload a gist with OOM details from dmesg and journalctl, if there is a way to get debug info for this, please let me know.

This happens at random intervals, mostly when firefox is being left idle. Since it starts >1000 threads, it easily fills ram and swap, then get killed by OOM killer. Hence no crash reports. I'll upload a gist with OOM details from dmesg and journalctl, if there is a way to get debug info for this, please let me know.

Svi odgovori (4)

Arda
Arda Vlasnik pitanja
more options

https://gist.github.com/Abrifq/01741049a57caf4227761476e0e6bc53

Has details from both dmesg and journalctl, showing the process count.

Arda
Arda Vlasnik pitanja
more options

Also, the OOM killing caused me to logout in some websites.

Maybe it corrupted cookies or corrupted cookies caused this?

Izmjenjeno od Arda

Paul
Paul
  • Moderator
  • Top 10 Contributor
more options

Hi

How many tabs do you currently have open in Firefox?

Arda
Arda Vlasnik pitanja
more options

Paul said
How many tabs do you currently have open in Firefox?

At the time of crash, around 10.

My system has 16GB and I was not doing anything resource intensive.