On 2025-02-11, Max Nikulin <maniku...@gmail.com> wrote: >>> >>> If Firefox is killed or crashes I believe you get the 'Restore Session' >>> page instead of the home page when you restart it (i.e. exactly the >>> option to retrieve your open tabs at the moment of the kill or crash). > > Are you killing Firefox just to avoid a couple of extra clicks to open > menu and to select "restore previous session" there? I hope, the code, > that saves current state to disk, is written having in mind that the > process can crash any time, so some consistent (but may be a bit > obsolete) state may be restored afterwards. I am in doubts if this > scenario is heavily tested (perhaps besides sqlite). From my point of > view, killing a process may noticeably increase a chance to get > corrupted data in comparison to closing the same application.
You would kill Firefox when it no longer responds to the canonical closing procedure (i.e. when the application has become unresponsive). I would suppose that its state is saved periodically so that upon restart the user has the option to restore that state. This is my personal experience with the browser. Your supposition concerning what might or might not be heavily tested is beyond the scope of my knowledge. >> then I zap fvwm and touch >> the power button. (First zapping fvwm avoids occasionally having to >> wait for a 90-second timeout to expire.) > > journalctl usually allows to identify processes causing timeouts. > Perhaps they should be just properly wrapped into systemd user units. > >
