-
Notifications
You must be signed in to change notification settings - Fork 89
Asyncio tasks are not destroyed #16
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
Comments
@belolap asyncio.Task internally relies on the GC, so you need to use weakref (or just wrap with another function): while True:
...
tasks = weakref.WeakSet(Task.all_tasks())
... |
The problem is here: graphql-ws/graphql_ws/aiohttp.py Line 115 in 660a0e0
when |
Is there any solution to that problem at the moment? |
Should work now in master |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Then I close ws connection to server after subscription some asyncio tasks are not destroyed. If I reload page of my webapp several times, there are a lot of existing tasks. It's possible memory leak.
Example app:
Task list after 3 connections. Full log attached.
logfile.txt
The text was updated successfully, but these errors were encountered: