Last updated on JULY 06, 2017
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.3 and later
Information in this document applies to any platform.
3 different client-side memory leaks have been observed in a 10.2 AQ OCI
client program when using OCIAQListen in conjunction with OCIAQDeq when using the valgrind massif heap profiler.
1. Issue 1 relates to memory allocated by OCIAQDeq after it has been invoked by OCIAQListen.
2. Issue 2 relates to some memory allocated by OCIDescriptorAlloc (called with OCI_DTYPE_AQMSG_PROPERTIES), while the corresponding OCIDescriptorFree
is correctly called.
3- Issue 3 is related to some memory allocated by OCIAQListen when it is called repeatedly while the queue has another session performing an dequeue which is not committed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms