Bug ID 742184: TMM memory leak

Last Modified: May 29, 2024

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

Known Affected Versions:
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, 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, 14.1.0, 14.1.0.1

Fixed In:
15.0.0, 14.1.0.2, 13.1.3

Opened: Aug 30, 2018

Severity: 2-Critical

Symptoms

-- High TMM memory utilization; -- Aggressive sweeper activated; -- the 'packet', 'xdata' and 'xhead' caches in the memory_usage_stat tmstat table have high 'allocated' and 'curr_allocs' numbers with a steadily increasing profile.

Impact

Degraded performance, possible TMM crash due to out-of-memory condition.

Conditions

A fastL4 and a L7 profile (e.g. HTTP) are assigned to a virtual server.

Workaround

Do not add a L7 profile to a fastL4 virtual server.

Fix Information

No memory leak in the TMM. Note: there are limits to what L7 profiles such as HTTP can do when attached to fastL4 virtual servers, and this fix does not change them. For more information see: -- https://support.f5.com/csp/article/K16446 -- https://support.f5.com/csp/article/K16783

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips