Bug ID 739846: Potential Big3D segmentation fault when not enough memory to establish a new iQuery Connection

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 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, 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, 13.1.1.2, 13.1.1.3, 14.0.0, 14.0.0.1, 14.0.0.2

Fixed In:
14.1.0, 14.0.0.3, 13.1.1.4, 12.1.4.1, 11.6.4, 11.5.9

Opened: Aug 09, 2018

Severity: 2-Critical

Symptoms

When the big3d runs out of memory for iQuery connections, a segmentation fault might occur.

Impact

Segmentation fault and big3d restarts. No statistics collection or auto-discovery while big3d restarts.

Conditions

-- Not enough memory to create additional iQuery connections. -- Receive an new iQuery connection.

Workaround

None.

Fix Information

The big3d process no longer gets a segmentation fault when reaching the limits of the memory footprint while trying to establish iQuery connections.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips