-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
TaskRunner
prevents Director from exiting
#592
Comments
I can get around this by changing the loop to |
oh, i thought it was zeromq that was preventing the exit, but it looks like it is any python thread. hmm. there is this signal you can catch:
if the user quits by closing the window, you can use the
then it exits fine. still not ideal. |
Ok, makes sense. Making the thread a daemon solves all of my immediate problems, so I'll go with that for now. |
Ok good. I still don't understand why it doesn't work. It seems like when the Qt event loop exits the Python thread loses it's ability to run. Code on the main Python thread runs fine, but calling thread.join() just hangs. I think it might have something to do with PythonQt deinitializing some python state. I'll let you know if I am able to debug it further. |
It looks like the
TaskRunner
itself is keeping the Director app alive even when the window is closed (or when ctrl+Q is pressed). To reproduce, launch thedrake-visualizer
app and then run (in the console):then close the Director console and main window. The
drake-visualizer
binary keeps running until youctrl+c
it from the terminal.I'm trying to figure out how to fix this, but haven't had any luck yet.
The text was updated successfully, but these errors were encountered: