Project

General

Profile

Actions

Bug #4778

closed

flow/bypass: app-layer/stream resources not freed when bypass activated

Added by Victor Julien 11 months ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
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.


Related issues 2 (0 open2 closed)

Related to Bug #4650: Stream TCP raw reassembly is leakingClosedVictor JulienActions
Copied to Bug #4971: flow/bypass: app-layer/stream resources not freed when bypass activatedClosedShivani BhardwajActions
Actions #1

Updated by Victor Julien 11 months ago

  • Status changed from New to In Review
  • Assignee set to Victor Julien
  • Target version set to 7.0rc1
Actions #2

Updated by Victor Julien 11 months ago

  • Related to Bug #4650: Stream TCP raw reassembly is leaking added
Actions #3

Updated by Victor Julien 11 months ago

  • Status changed from In Review to Closed
Actions #4

Updated by Shivani Bhardwaj 9 months ago

  • Label Needs backport to 6.0 added
Actions #5

Updated by Shivani Bhardwaj 9 months ago

  • Copied to Bug #4971: flow/bypass: app-layer/stream resources not freed when bypass activated added
Actions

Also available in: Atom PDF