"Configuration is already in use" sometimes appears after unexpected exit #73
Comments
special
added a commit
to special/ricochet
that referenced
this issue
Aug 16, 2014
QLockFile checks whether a process with the PID in the lock file exists, and assumes the lock is held if one does. In many cases that can result in false-positive "locked" errors, especially after unexpected reboots. It's very bad if we tell users that their configuration is in use when it isn't. To avoid this, try removing stale lock files automatically. On most systems, if the lock is truly held, the removal will fail and we can safely display the error. It's possible that this could allow users on networked filesystems to launch multiple instances, but that is less of a bug than the existing one. Fixes ricochet-im#73
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The configuration lock file uses a PID to check whether the application is active (through QLockFile), but that check is fragile. If the program doesn't terminate normally and that PID is reused, it will refuse to start, and this is very confusing.
The text was updated successfully, but these errors were encountered: