Bug ID 725792: BWC: Measure log-publisher if used might result in memory leak

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1

Fixed In:
14.1.0

Opened: Jun 26, 2018

Severity: 3-Major

Symptoms

When Measure is used in BWC with log publisher defined, it might result in a memory leak in tmm.

Impact

Memory leak in errdef.

Conditions

-- BWC dynamic policy is configured. -- Measure is enabled. -- Log-publisher is defined.

Workaround

There is no workaround other than not to enable Measure in the BWC dynamic policy.

Fix Information

Configuring Measure in the BWC dynamic policy no longer results in a memory leak.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips