-
Notifications
You must be signed in to change notification settings - Fork 45
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
qasync is getting stuck in an infinite loop after an uncaught exception #22
Comments
The original error looks like it might be an asyncio error, but I would not expect qasync to get stuck in an infinite loop because of it. |
Could you indicate how you got to that exception ? |
I'm getting the same one now, but with KeyError: 358. I think it happened after I added a background flask server on a daemon thread. When I hit stop in PyCharm, it enters an infinite loop and keeps spamming that error. |
If the isssue is still present, please provide a minimal, reproducible example. |
Summary
When closing an application after an uncaught exception in user code, qasync is getting stuck in an infinite loop at
qasync/qasync/__init__.py
Line 273 in cc5abcb
finally
block.NB the line numbers in the traceback below don't match master since I'm a few commits behind (one of the commits added some whitespace).
Full traceback is:
The text was updated successfully, but these errors were encountered: