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
Possible memory leak triggered by async #7532
Comments
I played around with dumpNumberOfInstances, it seems that the Futures are not being deallocated.
|
That's not even a bug afaict. You call |
Fixed in httpbeast. |
This is a fun one and I caught it thanks to my work on
httpbeast
.I was able to systematically create a short sample reproducing the issue with no dependencies (except on the stdlib).
WARNING: This allocates memory very quickly.
Click to expand old reproduction that depends on httpbeast
I wasn't able to reproduce this outside my project, so here is the code needed to reproduce it with ``httpbeast`` as a dependency:Tip: The
onRequestAsync
procedure is just what the{.async.}
pragma produces out of theonRequest
procedure defined above.Here is how I solved it, PR will be coming soon to generate this code:
The text was updated successfully, but these errors were encountered: