You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to use after_this_websocket to cleanup some long-running tasks that go alongside websocket connections. It appears this isn't called reliably enough for me to use it as a cleanup. My server has a memory leak right now and we think it's due to this.
Environment:
Python version: Tox 310 311
Quart version: 0.19.5 (current git tip)
I have reproduced this behaviour in the Quart tests: willstott101#1 I hope that's enough info to quickly confirm if this is a bug or accepted behaviour. The docs recommend we always re-raise the cancelled error in websockets which makes it impossible for us to use after_this_websocket for cleanup.
The text was updated successfully, but these errors were encountered:
I'm trying to use
after_this_websocket
to cleanup some long-running tasks that go alongside websocket connections. It appears this isn't called reliably enough for me to use it as a cleanup. My server has a memory leak right now and we think it's due to this.Environment:
I have reproduced this behaviour in the Quart tests: willstott101#1 I hope that's enough info to quickly confirm if this is a bug or accepted behaviour. The docs recommend we always re-raise the cancelled error in websockets which makes it impossible for us to use
after_this_websocket
for cleanup.The text was updated successfully, but these errors were encountered: