-
-
Notifications
You must be signed in to change notification settings - Fork 163
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SingleApplication implementation buggy #26
Comments
And additional bug: If one user runs qtpass, no other users will be able to run qtpass on the same machine on Linux (I suspect it might work ok on Windows, but haven't tested). |
I don't know what happened, but I now in over 50% of startup attempts get this message: |
I have not had any issues of that sort except for testing actively in the debugger (sometimes not cleanly closing the application). Looking into removing the local socket stuff entirely and going for something simpler (also trayicon support for those who like such things) @rdoeffinger would you think it's a nice option to have "single application" mode a configurable option? |
3fc1dc7 fixes part of this . . |
Unfortunately the SingleApplication implementation seems to be full of race conditions, e.g. when one application has started closing down but you are starting a new one (this one seems unavoidable by design) but there also seem to be other issues that mean that after a crash it is not possible to start a new instance for several seconds.
The latter seems to happen because the shared memory instance somehow lingers while the server does not respond.
It is probably fixable (by starting the application if the message is never acknowledged - but this just leads to other issue like that in some cases like extreme system load you can end up with multiple running instances after all), but is this feature really worth the amount of code and really annoying bugs?
Especially since as far as I can tell there are no too serious conflicts between 2 instances running at the same time, as qtpass has almost no internal state.
The text was updated successfully, but these errors were encountered: