You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you very much for the bug report, and sorry for taking a long time to reply, dont't know if you have already solved the problem, seems like I happened to ignore the issue notification email at the time.
According to your description, this can lead to serious consequences in certain scenarios. Unfortunately I'm not familiar with the memory leak debug tool you provided, could you please provide more detailed debug logs so that we can identify the exact location of the leak? According to my understanding that arose from your code on gist, it shows that using cursor object with context manager causes unreleased problem and calling close manually solves it? I am not sure if I understand it correctly.
Describe the bug
Potential memory leak in cursors context manager.
To Reproduce
Call many times cursor.fetchone().
Gist with sample code: https://gist.github.com/ilosamart/272a7dadb639f19fd62b7947ae12ab5f
It contains three versions of the same method: one async (this lib), one async (this lib) which explicitly closes the cursor, one with pure cx_oracle.
Expected behavior
I expected that the cursor context manager closed the cursor.
Platform:
Additional context
I used the instructions on https://oracle.github.io/odpi/doc/user_guide/debugging.html to debug memory alloc inside OCI.
The text was updated successfully, but these errors were encountered: