What's New with Firefox 142

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.

When trying to diagnose performance or memory issues with a browser, always start with the installed and enabled extensions.

Yep. Can’t upvote this enough.

Next up would be looking closer at the pages you frequent. I think many people would be surprised at all the ways web apps screw up these days.

All that said, the browsers, as unfair as it may seem, should do better at handling all of the slop that web app and extension developers put out there. It’s sometimes just a whole lot easier to make the browser more bulletproof than it is to make a bajillion JavaScript/python monkeys conscientious and competent.