Bug ID 470945: Memory leak in Export Policy operation

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(all modules)

Known Affected Versions:
11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.6.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.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4

Fixed In:
12.0.0, 11.5.6

Opened: Jul 09, 2014
Severity: 2-Critical
Related AskF5 Article:
K16891

Symptoms

Performing the Export Policy operation creates a memory leak.

Impact

If a long-lived process exports many security policies, the device can run out of memory.

Conditions

ASM is provisioned. A long-lived process exports many security policies without being restarted.

Workaround

Restart the long-lived process that exports many security policies with the following command: # pkill -f asm_config_server_rpc_handler.pl

Fix Information

A standard Perl package 'YAML::LibYAML' was upgraded to a newer version in order to prevent a memory leak that sometimes occurred after exporting a security policy.

Behavior Change