-
Notifications
You must be signed in to change notification settings - Fork 155
memory leak in logging usage #359
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Hello @if6was9, Java driver 1.2.2 was released yesterday and is now available in maven central. Could you please try it out to confirm that this issue is resolved? Thanks. |
Hello @if6was9, I'll close this issue assuming that fix in 1.2.2 and 1.3.0 works for you. Attached PR adds a logger count assertion to the stress test. Stress test was showing the same logger leak reported here. Thanks for reporting this problem! |
I believe the issue is resolved. Thank you. |
There is a severe memory leak here:
https://github.com/neo4j/neo4j-java-driver/blob/1.3/driver/src/main/java/org/neo4j/driver/internal/NetworkSession.java#L65
Our application ends up in GC hell after running for a few days. Here is a chart from new relic that shows this:
I'll submit a PR shortly.
The text was updated successfully, but these errors were encountered: