Bug ID 454692: Assigning 'after' object to a variable causes memory leaks

Last Modified: May 29, 2024

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

Known Affected Versions:
11.6.0, 11.5.1, 11.5.0, 11.4.1, 11.4.0

Fixed In:
12.0.0, 11.6.0 HF6, 11.5.1 HF6, 11.4.1 HF9

Opened: Mar 29, 2014

Severity: 4-Minor

Related Article: K16235


Assigning 'after' object to a variable prevents the release of the 'after' object and its related connflow object, resulting in a memory leak for 'connflow', 'tcl (variable)', 'tclrule_pcb', and 'filter (variable)'.


TMM crash or TMM memory usage increases.


This occurs when using the 'after' iRule command and assigning it to a variable.


Unset the variable containing the 'after' object, for example: when HTTP_REQUEST priority 800 { set SCRIPT_ID [\ after $static::one_second { log local0. "$LOG_MSG" } \ ] } when CLIENT_CLOSED { unset SCRIPT_ID }

Fix Information

Assigning 'after' object to a variable no longer causes memory leaks.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips