Bug ID 491554: [big3d] Possible memory leakage for auto-discovery error events.

Last Modified: May 29, 2024

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

Known Affected Versions:
11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 11.5.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.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.6.0, 11.6.1, 11.6.2, 11.6.3,,,,, 11.6.4, 11.6.5,,,, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF5, 11.5.3, 11.4.1 HF9

Opened: Nov 18, 2014

Severity: 4-Minor

Related Article: K54162409


The big3d process may leak memory. As a result of this issue, you may encounter one or more of the following symptoms: You notice a progressive increase in the amount of memory that the big3d process uses. The big3d process produces a core file in the /shared/core directory. The BIG-IP system unexpectedly fails over to another system in the device group. The monitoring system marks the monitored device as unavailable.


Memory usage for the big3d process increases, and may eventually affect other services and overall system performance.


This issue occurs when all of the following conditions are met: Your system is actively monitored by a BIG-IP GTM or Enterprise Manager system. The monitoring system is configured with discovery enabled. The big3d process returns error messages to monitor requests.



Fix Information

big3d no longer leaks memory during auto-discovery failure events.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips