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
Using Dr Memory could find the memory leak but the call stack is empty. So I suspect this issue is only seen on Windows and it is a 3rd party library memory leak issue as nothing is found on Linux. Need check more to confirm.
No memory leak is reported on Linux after open detect_memory_leaks and enable TestFetchScrollLast - ./ignite-odbc-tests --catch_system_errors=false --detect_memory_leaks=1
The text was updated successfully, but these errors were encountered:
When I worked on another issue, the following tests have found memory leaks. They are disabled for now as root cause has not been identified.
Notes:
Using Dr Memory could find the memory leak but the call stack is empty. So I suspect this issue is only seen on Windows and it is a 3rd party library memory leak issue as nothing is found on Linux. Need check more to confirm.
No memory leak is reported on Linux after open detect_memory_leaks and enable TestFetchScrollLast -
./ignite-odbc-tests --catch_system_errors=false --detect_memory_leaks=1
The text was updated successfully, but these errors were encountered: