Actions
Bug #4778
closedflow/bypass: app-layer/stream resources not freed when bypass activated
Affected Versions:
Effort:
Difficulty:
Label:
Needs backport to 6.0
Description
When a flow bypass is activated, the flow holds on to whatever memory is used in the app-layer and stream. These will finally be freed at the end of the flow. This is not efficient, as after the bypass no code paths will use the app-layer state, transactions or segments.
We might want to hold on to the Tcp session, as this is where TCP packet flags are taken from.
Updated by Victor Julien about 3 years ago
- Status changed from New to In Review
- Assignee set to Victor Julien
- Target version set to 7.0.0-beta1
Updated by Victor Julien about 3 years ago
- Related to Bug #4650: Stream TCP raw reassembly is leaking added
Updated by Victor Julien about 3 years ago
- Status changed from In Review to Closed
Updated by Shivani Bhardwaj almost 3 years ago
- Label Needs backport to 6.0 added
Updated by Shivani Bhardwaj almost 3 years ago
- Copied to Bug #4971: flow/bypass: app-layer/stream resources not freed when bypass activated added
Actions