Bug ID 483501: Access policy v2 memory leak during object deletion in tmm.

Last Modified: Oct 06, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP APM(all modules)

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5

Fixed In:
12.0.0, 11.6.0 HF6

Opened: Oct 08, 2014
Severity: 3-Major

Symptoms

A small memory leak everytime a per request access policy is deleted.

Impact

A small memory leak everytime a per request access policy is deleted.

Conditions

If the access policy delete was done before execute_access_policy' released the ref count, the access policy was getting deleted even though its still being used for one session. If the access policy delete was done when the access policy was not being used by any session, the access policy was not getting deleted.

Workaround

None

Fix Information

1) In 'access_policy_add', increment the access policy reference count before adding the access policy to the global access policy hash table. 2) In 'release_access_policy' dont return 'access_policy->ref_count' at the end of the function. The 'access_policy' could have potentially been deleted and freed by this point. The return value is not really used so just dont return any value.

Behavior Change