Because on my Linux machines, once it’s been updated, I can not open a new tab, it’ll tell me to frig off and restart. I can click links in existing tabs, and might’ve been possible to enter a new URL in an existing tab, I don’t recall exactly.
an application’s files can be updated while the application is running, and
there’s an OS-wide updater (i.e. package manager) with which you can update most software, including Firefox. (You can also get Firefox with its built-in auto-updater, but most people prefer the OS-wide updater.)
Both of these are good things. But Firefox, with its relatively advanced multi-process architecture, had a problem here, because it could happen that its files got updated while it was running and then when it started a new process, this new process might be incompatible with the old processes, therefore unable to communicate correctly.
Their initial solution was to force you to quit Firefox and reopen it, when they detected that the files had changed and you did something in Firefox which might need a new process, so primarily when opening a new tab.
I’m guessing, they now implemented a way to launch the new process by still using the old files from before the update.
Why?
Does one reboot their entire system after updating Firefox on Linux?
I never do. I don’t even restart Firefox after updating, if it is already running.
Clearly you don’t use it often, firefox will force you to restart itself and refuse to render webpages.
I guess I am lucky that it does not refuse to work since it is my default browser across all my machines.
Linux machines?
Because on my Linux machines, once it’s been updated, I can not open a new tab, it’ll tell me to frig off and restart. I can click links in existing tabs, and might’ve been possible to enter a new URL in an existing tab, I don’t recall exactly.
Can you even update Firefox while it’s running if you’re on windows?
No idea lol
On Linux:
Both of these are good things. But Firefox, with its relatively advanced multi-process architecture, had a problem here, because it could happen that its files got updated while it was running and then when it started a new process, this new process might be incompatible with the old processes, therefore unable to communicate correctly.
Their initial solution was to force you to quit Firefox and reopen it, when they detected that the files had changed and you did something in Firefox which might need a new process, so primarily when opening a new tab.
I’m guessing, they now implemented a way to launch the new process by still using the old files from before the update.