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.

Sign up for GitHub

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

Jump to bottom

call demo/pool.cpp compiled executable program in valgrind memory leak problem #38

Closed
ljx0305 opened this issue Apr 19, 2016 · 1 comment
Closed

call demo/pool.cpp compiled executable program in valgrind memory leak problem #38

ljx0305 opened this issue Apr 19, 2016 · 1 comment
Assignees
@vrogier
Labels
duplicate wontfix / wontdo

Comments

@ljx0305
Copy link

ljx0305 commented Apr 19, 2016

My Run platform： Linux redhat6.4 64bit、g++ 4.4.6、valgrind 3.2.1
valgrind log info:
log.txt
@vrogier
Copy link
Owner

vrogier commented Apr 19, 2016

Hi,

Duplicate issue with #26.
OCI is known for not releasing all allocated memory.
When looking at your valgrind ouput, it is memory allocated by OCI (that call OCILIB memory allocation callbacks). All memory or OCI handle allocated by OCILIB is released.
Thus, there is nothing I can do about.
You can google "Oracle OCI leak valgrind" and you will see that is an Orace Client issue.

Regards,

Vincent

@vrogier vrogier closed this as completed Apr 19, 2016
@vrogier vrogier self-assigned this Jan 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vrogier vrogier

Labels
duplicate wontfix / wontdo
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vrogier @ljx0305