-
Notifications
You must be signed in to change notification settings - Fork 163
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 in mongodb driver version 2.7 #978
Comments
Here is my cargo tree when i use version 2.7
And here is for version 2.6
Please tell me if i am doing something wrong, but after downgrading driver to version 2.6 memory does not grow. |
Hi! I've reproduced this and have a solid lead on what's going on - I expect to have a fix in on Monday, and we'll cut a 2.7.1 release for that. I'd also like to thank you for the most conscientious bug report I've ever seen, it made it very easy to pick up :) |
You are really kind. I just tried to be as helpful as I can :) Maybe You can share Your methodology, how to track crates / methods where the memory is allocated and never released? |
#979 should fix this :) I don't really have any special techniques to share, unfortunately - it sounds like you did what I would have. If my first guess at the issue hadn't been correct, I probably would have tried to use https://docs.rs/dhat/latest/dhat/. |
I can confirm that #979 fixed the issue for us. However... can we please push a new version asap as the current published crate has this leak and it's quite drastic! |
We'll be pushing a release tomorrow for this :) |
2.7.1 with this fix is now available. |
Versions/Environment
Describe the bug
Memory usage grows constantly on driver version 2.7, here is simple example program:
my Cargo.toml kools like this:
The X axis on graph is measured in seconds
See the graph below:
On version 2.6 memory looks perfectly fine:
Here is the full source code of working example https://github.com/jakudlaty/mongo-memleak-test/
The text was updated successfully, but these errors were encountered: