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
I can reproduce the leak, and it looks like it was fixed in ODBC Driver 18. If possible, I would recommend using Driver 18, if not the next release of Driver 17 (with the fix) would probably be next year.
This is a report regarding a bug in the odbc driver. I'm writing here because I don't know the appropriate place to report it.
(I also posted it here. https://learn.microsoft.com/en-us/answers/questions/1418766/memory-leak-in-microsoft-odbc-driver-17-10-5-for-s)
The following code:
compile command:
exec:
In this way, once I close the connection and connect it again, I will get a memory leak.
Regards.
The text was updated successfully, but these errors were encountered: