OCCI Leaks Memory in Connection Pool when using LDAP
(Doc ID 1553245.1)
Last updated on MARCH 02, 2019
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Executing a Multi-threaded (POSIX) OCCI application that uses connection pooling shows symptoms of a memory leak. i.e Some processes are growing in memory size or crash with a segmentation fault after running for some time.
The memory leak is specific to using LDAP and does not occur when using tnsnames or local naming resolution.
Profiling and Debugging tools such as Valgrind may show report output similar to the following:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document