Comment 5 for bug 1610534

So, I think I've found the cause to atleast part of the issue. Recently, the app broke again failing to remember my tabs at all.

Looking in my files, I noticed a ~/.local/share/webbrowser-app/session.json.lock file, even though the app wasn't running. The actual session file was absolutely fine, and still contained my session from a couple of weeks earlier, the app just wasn't loading it due to the lock file. Deleting the lock file had my old session back up and running.

Before I deleted it, I had a look at the lock file, and found that it was an empty file. I would have expected the app to write its PID into the lock file when creating it. Then, when the app opens and sees a lock file, it can check if the given PID exists, and if so exit. If the process no longer exists, then it can take over ownership of the lock file.

Perhaps implementing this kind of basic behaviour would be enough to fix this issue, as it looks like it may just be a crashing application failing to remove its lock file.