What is this related to?
What is this related to?
My reading is that if your package manager updates FF on disk while it's running, it can no longer guarantee that new tabs can be created safely, since creating a tab requires spawning a child process and the parent was created with an executable that no longer exists/knows anything about the executable it needs to use when spawning.
It is super annoying and I feel like there are some obvious fixes. I'm also not 100% sure why it only happens on Linux (it updates fine on Windows and MacOS while running right?)
(At least, as far as I can tell)
If you install, say, FDE directly on linux, you'll get the same behaviour.
But if you use the distro's package manager then I don't think there's a viable workflow for it, as the package manager doesn't have hooks into process management.
The package manager would probably have to be subsumed by systemd for that to even be feasible.
Or at least, you get an error if you try and modify an executable that is currently being used by a process on Windows.
But I suppose linux is generally geared towards servers, where that isn't an issue.
But if you install it through apt or some such package manager, the PM is doing the updates, and it doesn't take into account that Firefox is running.
[1] http://archive.mozilla.org/pub/firefox/releases/latest/READM... has instructions for getting a release tar.
The solution is to version the files and keep the old versions until the processes are closed. As Windows enforces because it doesn’t allow you to delete files that are in use.
Package is multiple files app needs replaced, so you have old app getting the files replaced under it during upgrade, that's why restart is needed.
In case of snap there is layer between, the "snap" is just a blob that is mounted by a daemon that then runs app off it.
If you just move/delete old snap the daemon should just be accessing old one till the app stops
On Linux, you can delete or replace open files, and even running applications. Instead of updates being handled by dozens of individual updaters that coordinate closely with each app so that updates happen between restarts, updates happen in the background without really coordinating with running apps.
Sometimes, after Firefox has been updated, there's some kind of incompatibility between the old running binary and the new assets (internal JS, CSS, and idk what else). In that case, Firefox can't open new tabs because you're still running the old binary, which doesn't work with the new assets which have been installed, or which is looking for old assets that it opens dynamically at runtime that are simply no longer present on your disk.
I don't know how the "behind the scenes" work but you can run an update while Firefox is running. We do it all the time. We push security updates to our clients via an agent. It runs the official installer in silent mode. It is like OP described: You can't open new tabs (ok you can but they will not work) until you restart the browser, but the existing tabs keep working.