←back to thread

What's New with Firefox 142

(www.mozilla.org)
177 points keepamovin | 1 comments | 02 Sep 25 10:50 UTC | HN request time: 0s | source
Show context
Shank ◴[02 Sep 25 12:44 UTC] No.45102381[source]▶
Lately, I’ve experienced memory leaks in Firefox that I’m too amateur to diagnose, that leads to Firefox eating 8gb of memory in some web renderer process. So when I excitedly check the changelog hoping for a summary of possible changes, I’m disappointed that there isn’t a verbose changelog for advanced users. I’m sure I could search bugzilla, but it makes me sad that the only “important” things are the headlining features.
replies(9): >>45102502 #>>45102585 #>>45102680 #>>45102814 #>>45102888 #>>45102942 #>>45102998 #>>45104100 #>>45105037 #
1. Anthony-G ◴[02 Sep 25 13:12 UTC] No.45102680[source]▶
I’ve had similar issues running the latest Firefox (currently 142 as per this discussion) on the latest Fedora (42). I used to be able to lock the screen and go home but I’ve recently had a couple of mornings where I’d come into work and find my system unresponsive. I use the Magic SysRq command to trigger the OOM (out-of-memory) killer as many times as required to free up enough resources that I could log in on a virtual console (Alt-Ctrl-F2). This would allow me to manually kill Firefox, freeing up about 15GB of RAM and all 16GB of the swap file.

I’ve been too busy with work to spend any time investigating the cause. At first I had been blaming the `teams-for-linux` electron app but figured that wasn’t the culprit because I close it every evening. In Firefox, `about:processes` is useful while actually using the application but I’m not really sure how best to diagnose what’s happening after the fact.