Bug ID 435367: Memory leak possible in conditions related to a large memory allocation to wam::wam_bitset_bits

Last Modified: May 29, 2024

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

Known Affected Versions:
11.0.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1

Fixed In:
11.5.0, 11.4.1 HF4

Opened: Oct 25, 2013

Severity: 2-Critical

Related Article: K15705


TMM may core due to memory leak, and the core file indicates a large memory allocation to wam::wam_bitset_bits


Reduced capacity and possible cores for low memory.


This occurs when modifying the configuration. Each configuration change may leak a small amount of memory; scripts or other utilities which change the configuration frequently may encounter low memory situations. Whether the configuration will cause a leak is dependent on the configuration itself. This will be reflected in tmctl memory_usage_stat, with wam::wam_bitset_bits showing an abnormally high allocation. After a restart and configuration load, the current allocation should be zero; after running traffic the current allocation may be correct when non-zero.



Fix Information

This release fixes a memory leak related to a large memory allocation to wam::wam_bitset_bits, so the leak no longer occurs.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips