Last Modified: Feb 20, 2019
See more info
Known Affected Versions:
14.0.0, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52
Opened: Aug 14, 2018
In some execution paths of per-request policies, policy ref count gets unbalanced and causes a core dump and/or memory leak.
Memory leak (in case of per-session policy not released). It may cause a core dump in some cases, if the per-request policy is over-released.
This is a very rarely occurring issue encountered when using per-request policies.
This has been addressed in two ways; -- To prevent the core, the system now ensures that the per-request policy ref-count never goes below 1 while executing per-request policies. - To prevent the memory leak, corrected the instances in which policy was not released.