Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP All
Known Affected Versions:
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, 14.0.0, 14.0.0.1, 14.0.0.2
Fixed In:
14.1.0, 14.0.0.3, 13.1.1.2
Opened: Jun 20, 2018 Severity: 2-Critical
The Server/Application State Protocol (SASP) monitor, sasp_gwm memory usage slowly increases over time.
sasp_gwm grows over time and eventually the system may be pushed into swap. Once swap is exhausted, the Linux OOM killer might terminate critical system processes, disrupting operation.
The Server/Application State Protocol (SASP) monitor is configured. The leakage occurs during normal operation of the monitor and is not tied to any specific user or traffic action.
Periodic restarts of sasp_gwm processes avoids the growth affecting the system.
The sasp_gwm monitor no longer leaks memory when processing messages.