Project

General

Profile

Actions

Task #570

open

tracking: memory fragmentation

Added by Victor Julien about 10 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
Effort:
Difficulty:
Label:

Description

During start up (mostly detection engine init) we alloc and free enormous amounts of small memory blocks. This leads to memory fragmentation.

This task is a place holder for tracking that. Addressing all/most of this is going to be a long term effort.


Files

fragmentation-leak.png (150 KB) fragmentation-leak.png Gianni Tedesco, 05/24/2021 11:26 PM

Subtasks 3 (1 open2 closed)

Bug #492: memory not released after live rule swapClosedAnoop Saldanha06/30/2012Actions
Optimization #564: pattern id: rewrite pattern id assignmentClosedAnoop Saldanha09/28/2012Actions
Optimization #573: reduce allocs in signature parsingNewOISF DevActions
Actions

Also available in: Atom PDF