Bug ID 1587837: Memory leak in multiple components

Last Modified: Apr 19, 2025

Affected Product(s):
F5OS F5OS, F5OS-A, F5OS-C, Velos(all modules)

Known Affected Versions:
F5OS-A 1.3.2, F5OS-A 1.5.2, F5OS-C 1.6.2

Fixed In:
F5OS-C 1.8.0, F5OS-A 1.8.0, F5OS-A 1.5.3

Opened: May 22, 2024

Severity: 3-Major

Symptoms

A mishandling of memory allocation in the data provider callback library can cause memory allocation to grow over time. This memory usage growth can cause poor performance and the Out Of Memory (OOM) killer may kill components, causing outages.

Impact

Components may crash or get killed.

Conditions

If a data provider processes overlapping requests it can leak memory. The components most affected by this are the platform-stats, snmp-service, an L2 agent.

Workaround

Monitor memory usage and periodically restart daemons that experience excessive memory growth. On a chassis system, a manual failover and the rebooting the standby controller will restart all daemons. To minimize the occurrence of this leak, do not constantly poll for statistics, especially from multiple monitoring stations.

Fix Information

The library has been fixed to no longer leak session data.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips