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

Calling OCI_SetTrace() will cause small memory leak in OCI_ConnectionFree() #144

Closed
vrogier opened this issue Feb 21, 2018 · 1 comment
Closed

Calling OCI_SetTrace() will cause small memory leak in OCI_ConnectionFree() #144

vrogier opened this issue Feb 21, 2018 · 1 comment
Assignees
@vrogier
Labels
ocilib bug

Comments

@vrogier
Copy link
Owner

vrogier commented Feb 21, 2018

Calling OCI_SetTrace() the first time allocate a OCI_TraceInfo structure store in the OCI_Connection object that was not freed in OCI_ConnectionFree().

This is a minor memory leak as it is about 200 bytes in ANSI builds
@vrogier vrogier self-assigned this Feb 21, 2018
@vrogier
Copy link
Owner Author

vrogier commented Feb 21, 2018

Fixed by commit bc6b4f1

@vrogier vrogier closed this as completed Feb 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vrogier vrogier

Labels
ocilib bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vrogier