2 ms·
This is exactly right. And this happens because it needs to load libraries or exec subprocesses that aren't compatible between versions. Since the matching vers
by kevincox 4y ago
This is exactly right. And this happens because it needs to load libraries or exec subprocesses that aren't compatible between versions. Since the matching version of the file has been replaced with a newer one it doesn't really have a choice, it is unable to launch the new tab. The nice message is a better alternative than crashing.
This also doesn't occur on NixOS because the new version is in a different direcotry and the old version is kept until it is garbage collected.
- vetinari 4y ago> This also doesn't occur on NixOS because the new version is in a different direcotry and the old version is kept until it is garbage collected. Also with flatpak; you are using the old version until you close it. Then it will be garbage collected. On the next launch, you will be running a new version from different root.
- account42 4y agoThis is 100% something that can be fixed by the browser. Package updates don't change existing files but rather create new files and update the filesystem to point to them. All it takes to not need a restart is to keep file handles open for all needed resources and forking from such a process instead of exec()ing new ones. Not entirely trivial for applications as monstrously complex as browsers but hardly comparable to other challenges they need to solve. It's only because they can control the update process on the OS they care about (Windows) that they don't bother.