You must be one of today's lucky 10000 [1].
[1] https://xkcd.com/1053/Forgot your link [1]
(Fortunately I was able to figure out what was going on and restored the previous window.)
Also, the automatic "check before exiting FF" got turned off somehow.
So, yeah, lots of fun surprises to deal with.
If you are dealing with normal amounts of memory usage and you have less than 16GB you may consider upgrading RAM considering this is as little as $40-60 at this point and well worth the look.
The check before closing multiple tabs didn't get turned off somehow the default changed in 2021 to default unchecked.
Lastly the behavior regarding closing the last window closing Firefox remains unchanged. It does in fact still work that way. If it didn't properly close I would suggest that is a bug or a second window on another workspace. If all you desire is to restart as opposed to actually closing firefox you can trigger a restart in about:profiles this has the benefit of working no matter how many windows you have open.
Obviously not, since the memory usage is increasing without bound despite no corresponding increase in memory-intensive tabs. Thanks for suggesting an alternate workaround for the collection failures though.
>If you are dealing with normal amounts of memory usage and you have less than 16GB you may consider upgrading RAM considering this is as little as $40-60 at this point and well worth the look.
I have 32 GB, which it (thankfully) hasn't come close to, but would, if I weren't periodically restarting. Kinda funny how we automatically don't expect 16 GB to be enough memory for text/image web pages though.
>The check before closing multiple tabs didn't get turned off somehow the default changed in 2021 to default unchecked.
Makes sense, I think it was a while since I was shocked to see that behavior.
>Lastly the behavior regarding closing the last window closing Firefox remains unchanged. It does in fact still work that way. If it didn't properly close I would suggest that is a bug or a second window on another workspace.
No other workspaces, so probably a bug. I found this report of something very similar, though on Mac rather than Windows:
https://bugzilla.mozilla.org/show_bug.cgi?id=1772056
>If all you desire is to restart as opposed to actually closing firefox you can trigger a restart in about:profiles this has the benefit of working no matter how many windows you have open.
Thanks, but I'd prefer the option that can be done with a few quick key commands, and Firefox isn't customizable in that way anymore.
Your memory usage growing without bounds on the other hand is obviously a bug. I would create a fresh profile and see if you can reproduce this behavior without extensions and report it.
You know ```Ctrl+shift+t``` this opens the last closed tab and - at least in chrome - restores the previous environment after restart
If these complaints come up every release, then perhaps they aren't "incredibly-niche" after all. At least not what they represent in aggregate.
Browsers remind me a lot of superstores and why successful ones go out of their way to stock low-volume specialty items despite them having low profit margins, costing more to handle and stock, and having a very small subset of their customers care enough to buy them:
1. Customers will usually go to a store that's further away from them if it has 100% of the items they want even when your store is much closer but only has 95%.
2. Cut enough of those low-volume items and you'll become that 95% store for most of you customers.
What the team steering firefox need to understand is that the average user is a myth. The average user does not exist. Every user is unique and has their own set of peculiarities. If you remove enough functionality based on telemetry or your own limited perception of what "niche" is (hello, gnome!), everyone will eventually be affected.
I think most of Firefox's hemorrhaging of users today is because Firefox became a 95% browser for most developers and users.
Most of the comments on every new Firefox release post are just as bad and have nothing to do with the actual release (folks whining about how their incredibly-niche use-case isn't supported anymore which breaks their workflow etc.), so in some ways it's nice to see something positive (which I would wager is more representative of the average user).