On 11/02/2025 08:08, David Wright wrote:
On Mon 10 Feb 2025 at 17:18:34 (-0000), Greg wrote:
On 2025-02-10, Max Nikulin wrote:
I am against suggestions to *kill* applications as well, unless it is
the last resort measure. It increases chance to lost data stored in
browser profile (list of opened tabs, passwords, etc.).
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.
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.
