Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Learn More

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

  • 4 wotmołwy
  • 0 ma tutón problem
  • 24 napohladow
  • Poslednja wotmołwa wot 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.

Wšě wotmołwy (4)

more options

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

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

more options

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

Maybe it corrupted cookies or corrupted cookies caused this?

Wot Arda změnjeny

more options

Hi

How many tabs do you currently have open in Firefox?

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.