Project

General

Profile

Actions

Bug #991

closed

threshold mem leak

Added by Victor Julien about 11 years ago. Updated about 11 years ago.

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

Description

~~Dr.M~~ Error #1: LEAK 36 direct bytes 0x0a8d1d90-0x0a8d1db4 + 0 indirect bytes
~~Dr.M~~ # 0 replace_malloc                          [/work/drmemory_package/common/alloc_replace.c:2292]
~~Dr.M~~ # 1 DetectThresholdEntryAlloc               [/home/victor/dev/oisf/src/detect-engine-threshold.c:181]
~~Dr.M~~ # 2 ThresholdHandlePacketHost               [/home/victor/dev/oisf/src/detect-engine-threshold.c:240]
~~Dr.M~~ # 3 PacketAlertThreshold                    [/home/victor/dev/oisf/src/detect-engine-threshold.c:600]
~~Dr.M~~ # 4 PacketAlertHandle                       [/home/victor/dev/oisf/src/detect-engine-alert.c:107]
~~Dr.M~~ # 5 PacketAlertFinalize                     [/home/victor/dev/oisf/src/detect-engine-alert.c:235]
~~Dr.M~~ # 6 SigMatchSignatures                      [/home/victor/dev/oisf/src/detect.c:1551]
~~Dr.M~~ # 7 Detect                                  [/home/victor/dev/oisf/src/detect.c:1697]
~~Dr.M~~ # 8 TmThreadsSlotVarRun                     [/home/victor/dev/oisf/src/tm-threads.c:559]
~~Dr.M~~ # 9 TmThreadsSlotProcessPkt                 [/home/victor/dev/oisf/src/tm-threads.h:142]
~~Dr.M~~ #10 PcapFileCallbackLoop                    [/home/victor/dev/oisf/src/source-pcap-file.c:154]
~~Dr.M~~ #11 libpcap.so.0.8!?                       +0x0      (0xb75a55cb <libpcap.so.0.8+0x1a5cb>)

Can be reproduced reliably with sandnet.pcap and rbn.rules

Actions #1

Updated by Victor Julien about 11 years ago

  • Target version changed from 2.0beta2 to TBD

Can't reproduce this anymore.

Actions #2

Updated by Victor Julien about 11 years ago

  • Target version changed from TBD to 2.0rc2

Saw it again, it's hard to reproduce it seems. Need to carefully review the code paths.

Actions #3

Updated by Victor Julien about 11 years ago

  • Status changed from Assigned to Resolved
  • Target version changed from 2.0rc2 to 2.0beta2
  • % Done changed from 0 to 90
Actions #4

Updated by Victor Julien about 11 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 90 to 100

Looks like the bug is gone indeed.

Actions

Also available in: Atom PDF