Skip to content
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

memory leak when inserting using ODBC connector #152

Closed
aleks-f opened this issue Apr 12, 2013 · 6 comments
Closed

memory leak when inserting using ODBC connector #152

aleks-f opened this issue Apr 12, 2013 · 6 comments
Assignees
Labels
Milestone

Comments

@aleks-f
Copy link
Member

aleks-f commented Apr 12, 2013

http://pocoproject.org/forum/viewtopic.php?f=12&t=2471

@ghost ghost assigned aleks-f Apr 12, 2013
@giovani-milanez
Copy link

The leak happens also when updating

@aleks-f
Copy link
Member Author

aleks-f commented Apr 22, 2013

I tracked this down to the SQLDescribeColW call in Unicode_Win32.cpp. With PostgreSQL 9.01.01.00 ODBC driver; process memory usage increases by 4k exactly on every sixth call to this ODBC API and is never released.

If anyone can shed some light on this, speak up. I was not able to find a leak in Poco::Data::ODBC.

@aleks-f
Copy link
Member Author

aleks-f commented Apr 26, 2013

Discussion continued in the forum.

@aleks-f
Copy link
Member Author

aleks-f commented Apr 27, 2013

Tested SQL Server and Oracle drivers on Windows, no leaks.

@aleks-f
Copy link
Member Author

aleks-f commented Jun 7, 2013

To the best I was able to determine, this was PostgreSQL driver leak. Closing.

@krishnavivek
Copy link

As you mentioned above, the issue is in psqlodbc driver leak.
Following is the link for the issue:
http://www.postgresql.org/message-id/5143041A.20605@vmware.com

The fix is present in latest releases.
I have used psqlodbc-09.03.0400.tar.gz. Memory leaks are no longer detected.

Thank You

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants