-
Notifications
You must be signed in to change notification settings - Fork 21
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 Leak #169
Comments
Hey @thiagopromano, thanks for the detailed issue, I'll try to check it this weekend |
@thiagopromano I fixed the memory leak, if possible can you test {:vix, github: "akash-akya/vix", branch: "fix-bug-169"} I think I introduced this bug during a recent change. I should invest sometime in creating automated checks for catching things like this in regression. I'll merge and cut a release soon. |
Hey @akash-akya, we've tested it and it is definitely fixed. Thank you so much for spending your time with this project! |
@thiagopromano FYI, pushed a new release with the fix -- https://hex.pm/packages/vix/0.31.0 |
Hey, it seems there is a memory leak on Vix/Vips, probably on the Operation pipeline.
I've opened an issue on Image as I found the problem there initially, but after digging through the code, the problem is on Vix.
This is an example where the leak can be reproduced, it calculates the dhash of an image.
It can be saved to a file such as
leak.exs
on the root and run asmix run leak.exs
.Note that the memory usage increases and it isn't reported by the Erlang carriers, which points to a leak on the NIFs. It also greatly surpasses the reported cache size on
Vix.Vips.tracked_get_mem/1
.Also, it is never freed until the BEAM stops.
The text was updated successfully, but these errors were encountered: