Project

General

Profile

Actions

Bug #7003

closed

Suspected memory leak after Suricata binary is updated or upgraded

Added by Samiux A 2 months ago. Updated about 2 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Affected Versions:
Effort:
Difficulty:
Label:

Description

When Suricata binary is updated or upgraded, the memory consumption is more than a double, e.g. memory used 1.8gb (before upgrade/update), memory used 5.0gb (after upgrade/update). The memory cannot be released even restarted Suricata with systemctl command. However, a system reboot can solved the problem. It is a high risk for a system with limited memory.

Actions #1

Updated by Samiux A about 2 months ago

Please close this thread as I misconfigured the Suricata. There is no such problem. Thanks a lot.

Actions #2

Updated by Muttanna Hosur about 2 months ago

Samiux A wrote in #note-1:

Please close this thread as I misconfigured the Suricata. There is no such problem. Thanks a lot.

@Samiux A Can you please share what configuration of Suricata caused extra memory consumption?

Actions #3

Updated by Victor Julien about 2 months ago

  • Status changed from New to Rejected
  • Assignee deleted (OISF Dev)
  • Priority changed from High to Normal
  • Target version deleted (TBD)
Actions

Also available in: Atom PDF