-
Notifications
You must be signed in to change notification settings - Fork 7
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
Memory is not being released #51
Comments
Hello sir, here is alternative;Base Code: Implementation to dotnet: |
See #49. |
You can't achieve anything by throwing such a stupid bad emoji sign, you need to have a basis, and I will say that you don't have it. |
I noticed that after I either use
Hash()
orVerify()
functions, memory drastically increases but is not released. My service will go from around 150MB to 600 MB+ which is what is supposed to happen, right? Since that is point of Argon2, to be memory heavy, right? But memory is not released and service is just running with 600+ MB from now on.I tried to explicitly call
GC.Collect()
after Argon2 functions, and it releases some because then memory usage is around 450 MB which is better but still not good. I also tried to explicitly dispose my DbContext which also drops memory usage for about 100 MB more but I don't understand why that is even happening. If I turn off all Argon2 functions (comment all Argon2 code), service runs with around 150MB and DbContext has not effecting it ever.I suspect there is some issues with garbage collection with Argon2.
The text was updated successfully, but these errors were encountered: