-
Notifications
You must be signed in to change notification settings - Fork 33
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 detected while using r2dbc-mssql 1.0.2 #279
Comments
Good catch. We eagerly allocate a buffer in the |
We encountered the same error but for |
And another one for
|
Been running into this issue as well. Could the issue be due to the change to Every time a connection timed out I would see a leak warning with leak detection set to paranoid. This is what initially lead me to believe it's an issue when |
We have encountered a similar memory leak and are currently working on a local fix. It appears that the repository is no longer actively maintained. While we could submit a Pull Request to share our changes, it seems unlikely that a new release will be published. |
This would be highly appreciated to see what you've changed to address the issue.
It is a proper perspective on the current state. With me as sole maintainer, things have changed in a way that a big chunk of my team was laid off in the past year and I have now even less bandwidth to maintain that project. I've attempted to dig into these memory leaks a couple times and I do not have the time to spend on a couple days for another attempt. Microsoft doesn't seem interested in maintaining the driver as well and so that is the fate of single-maintainer projects with little free time. That being said, I appreciate if the community would engage in maintenance as that is what this project needs the most. |
I appreciate that you're attentive to community feedback.
While we haven't yet found a complete fix, we will be operating with this warning for the moment due to budget constraints. Thank you for your response! :) |
We had the same error as @kijanowski, in our case during service startup when the ConnectionFactory bean was being created. Until this gets fixed, for us the issue went away by downgrading to 1.0.1.RELEASE so it looks like the issue has been introduced with the changes from the latest release. Edit: We had to use 1.0.0.RELEASE in the end due to #271 |
I am getting the following error during the tests with r2dbc-mssql 1.0.2.RELEASE
It might be caused by some not released buffers.
The text was updated successfully, but these errors were encountered: