Project

General

Profile

Actions
Copy link

Bug #4650

closed
PM VJ

Stream TCP raw reassembly is leaking

Bug #4650: Stream TCP raw reassembly is leaking

Added by Peter Manev over 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Victor Julien
Target version:
7.0.0-beta1
Affected Versions:
6.0.3, git main
Effort:
Difficulty:
Label:

Description

(originally reported y Eric Leblond)

It seems we have a leak in memory when TCP raw reassembly is enabled. Raw reassembly memuse is always going up. When deactivating it, the leak is gone. The leak seems to affect the flow that get cleaned far slowly.
Application layer triggering raw reassembly on TX border is helping a lot to reduce memory usage.

Peter to create a reproducible setup with trex.

Related issues 7 (0 open — 7 closed)

Related to Suricata - Bug #4502: TCP reassembly memuse approaching memcap value results in TCP detection being stoppedClosedVictor JulienActions
Related to Suricata - Bug #4766: Flow leaked when flow->use_cnt access race happensClosedVictor JulienActions
Related to Suricata - Bug #4778: flow/bypass: app-layer/stream resources not freed when bypass activatedClosedVictor JulienActions
Related to Suricata - Bug #4808: flow: worker-evicted flows need to be processed quickerClosedVictor JulienActions
Related to Suricata - Optimization #4653: Flow cleaning with chunked approach is memory hungryClosedVictor JulienActions
Related to Suricata - Optimization #4652: GAP handling improvements seem expensiveRejectedActions
Related to Suricata - Bug #4828: flow: flows not evicted & freed in timeClosedVictor JulienActions
Actions
Copy link

Also available in: PDF Atom