Memory Leak in FlistToStr Called During PCM_OP_CUST_COMMIT_CUSTOMER
(Doc ID 2466306.1)
Last updated on MAY 20, 2022
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.17.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
-----------------------
Memory leak is observed in flistToStr function called during PCM_OP_CUST_COMMIT_CUSTOMER to create an account associated with a business profile.
DETAILS
-----------------------
- During customer creation with OP_CUST_COMMIT_CUSTOMER opcode, by passing a business profile object in the input flist, pin_business_profile.xml script gets called inside which there is a call to flistToStr
- Memory leaks are being caused due to flistToStr function used in pin_business_profile.xml, while printing debug messages as shown in below line :-
pinlog(3, "Search Flist\n" + flistToStr( search ) ); - If this line (for printing these debug messages) is commented, memory leaks are getting reduced which clearly indicates that memory leaks are present in flistToStr
- BayMem tool has been used in these tests to detect the memory leaks.
- Below is a snippet from the report showing the stack trace of one such memory leak :
EXPECTED BEHAVIOR
-----------------------
There should be no memory leak.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |