4 ms·

Here, on Arch, Firefox updates don't cause me any grief. Only time I've ever need to reboot is after a kernel or DKMS module update. For systemd updates, I can

by Valmar 9y ago

Here, on Arch, Firefox updates don't cause me any grief. Only time I've ever need to reboot is after a kernel or DKMS module update. For systemd updates, I can just reload it. For the likes of core components like bash, and major DE updates, I can just lazily use loginctl to terminate all of my sessions, and start fresh. I'm not sure why Firefox would be causing instability until you restart (reboot?), though.

postingatwork 9y ago
Firefox with e10s enabled (all current releases) detects version differences between parent process and and a child process started at a later point in time. Until recently it aborted the entire browser when that happened. I think now they have some logic that tries to keep running with the already open processes and abandoning the incompatible child. Ideally they'd just prefork a template process for children and open fds for everything they need, that way such a detection wouldn't be necessary.
rlpb 9y ago
> I'm not sure why Firefox would be causing instability until you restart (reboot?), though. I get the impression that the UI loads files from disk dynamically, which start mismatching what was already loaded.