-
-
Notifications
You must be signed in to change notification settings - Fork 320
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
Find and fix memory leak #389
Comments
We have to check if this is still an issue in the current 1.8.0 or close it |
When we create 400 sessions in heroku, we see a rise from 313 mb to 320. When the sessions are expired, we go back to 316 mb. so there seems to be 3 megabyte leaking... this should not be a problem unless we play centralized CTFs on hosts with little ram, while folks doing all sorts of DAST testing in the hope to find secrets... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
after running
hey
twice against/challenge/1
we see that the amount of sessions build up to 400, and memory consumption goes from 200Mb to 277 MB after which, when all sessions are released, we still see 274 MB in use (e.g. 70 MB is not GCed?)The text was updated successfully, but these errors were encountered: