-
-
Notifications
You must be signed in to change notification settings - Fork 503
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
Potential memory leak when accessing the Diagnostics attribute of an IntegrityError #557
Comments
dvarrazzo
added a commit
that referenced
this issue
May 23, 2017
Triyng to fix a reported memory leak with diags, but implementing traversing doesn't help. Quite the opposite in the example provided in bug #557, the leak is present even with the `del diag`. The leak appears with Python 3.5, not with Python 2.7.
Thank you for the report and the script to reproduce, @davidcoffin ! I've played a bit with it... only to make it worse: implementing object traversal in the Diagnostics object makes only sure that the leak stays there even with the I'll look further into it... |
Closed
What is the latest progress? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We recently had a memory leak on one of our servers and it stopped as soon as we commented out the line of code assigning the Diagnostics attribute of an IntegrityError to a local variable within the exception handler.
The code below replicates the issue for Python 3.5.2, Psycopg 2.6.1. When I run this the amount of resident memory used by the process steadily increases, although not every time func() is called.
The text was updated successfully, but these errors were encountered: