-
Notifications
You must be signed in to change notification settings - Fork 664
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
multipassd SIGSEGV on clean while launching #585
Labels
Comments
It turns out this is a thread-synchronization problem: one thread is still processing the launch after another deleted the instance. In here it was after The agreement to address this is to use |
townsend2010
pushed a commit
that referenced
this issue
Feb 22, 2019
Due to how we are interacting with the Qt event loop, it's possible to crash when deleting an instance while it's still launching. The after effect of this is that concurrent client connections will block until launch (or other long running commands) finishes. A plan has been fleshed out to alleviate the concurrent blocking and will be implemented later. Fixes #585
townsend2010
pushed a commit
that referenced
this issue
Feb 22, 2019
Due to how we are interacting with the Qt event loop, it's possible to crash when deleting an instance while it's still launching. The after effect of this is that concurrent client connections will block until launch (or other long running commands) finishes. A plan has been fleshed out to alleviate the concurrent blocking and will be implemented later. Fixes #585
bors bot
added a commit
that referenced
this issue
Feb 22, 2019
632: qemu: Remove QCoreApplication::processEvents() to avoid a crash r=ricab a=townsend2010 Due to how we are interacting with the Qt event loop, it's possible to crash when deleting an instance while it's still launching. The after effect of this is that concurrent client connections will block until launch (or other long running commands) finishes. A plan has been fleshed out to alleviate the concurrent blocking and will be implemented later. Fixes #585 Co-authored-by: Chris Townsend <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Backtrace:
The text was updated successfully, but these errors were encountered: