this post was submitted on 26 Jun 2025
98 points (100.0% liked)

Linux

8249 readers
262 users here now

A community for everything relating to the GNU/Linux operating system

Also check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] dditty@lemmy.dbzer0.com 53 points 1 week ago (2 children)

Also:

On Linux Firefox uses less memory and no longer requires a forced restart after an update has been applied by a package manager

Super minor QoL update but I am all here for it!!

[–] victorz@lemmy.world 24 points 1 week ago

Was about to make the very same comment! That's awesome to me! So many times I've held an update to Firefox, while updating the rest of the system, just because I wasn't ready to restart my browser. This is great.

[–] Kusimulkku@lemm.ee 3 points 1 week ago (1 children)

It says package managers but I don't remember seeing any forced restarts with flatpak. I just now updated Firefox but it doesn't force anything. I just won't be using the new version before restarting it.

I don't remember it happening with system packages either on my system but it's been quite a while since I've updated that one.

[–] oktoberpaard@feddit.nl 2 points 1 week ago (1 children)

With flatpak updates, new tabs usually show a message that the browser needs to be restarted, or that something failed, I don’t remember exactly. At least that’s what happens on my machine.

[–] Kusimulkku@lemm.ee 1 points 1 week ago (1 children)

I know I've seen that on Windows and I think on Linux before, but I did a test when writing that post where I updated and then opened a new tab and even a new instance of Firefox and it didn't bother me about restarting. Weird

[–] Redjard@lemmy.dbzer0.com 2 points 1 week ago

You need a few new tabs in the same instance, until it tries to start a new process. I can usually keep using ff for half an hour before running into it.