Actions
Bug #2229
closedmem leak AFP with 4.0.0-dev (rev 1180687)
Affected Versions:
Effort:
Difficulty:
Label:
Description
==17538==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 2750112 byte(s) in 17 object(s) allocated from:
#0 0x4bf398 in __interceptor_malloc (/usr/local/bin/suricata+0x4bf398)
#1 0xb7e197 in AFPSetupRing /home/pevman/tests/git/oisf/src/source-af-packet.c:1836:24
#2 0xb6e054 in AFPCreateSocket /home/pevman/tests/git/oisf/src/source-af-packet.c:2029:15
#3 0xb6211c in ReceiveAFPLoop /home/pevman/tests/git/oisf/src/source-af-packet.c:1391:13
#4 0xc60fd9 in TmThreadsSlotPktAcqLoop /home/pevman/tests/git/oisf/src/tm-threads.c:334:13
#5 0x7fdf79dcd6b9 in start_thread (/lib/x86_64-linux-gnu/libpthread.so.0+0x76b9)
SUMMARY: AddressSanitizer: 2750112 byte(s) leaked in 17 allocation(s).
Details attached.
Files
Updated by Victor Julien about 7 years ago
- Status changed from New to Assigned
- Assignee set to Eric Leblond
- Target version set to 70
Strange, I thought Eric just fixed a leak. This seems to be with tpacket3
Updated by Victor Julien almost 7 years ago
It seems this was fixed during 4.1dev, or do you still see this Peter?
Updated by Peter Manev almost 7 years ago
- Status changed from Assigned to Closed
- Target version changed from 70 to 4.1beta1
Correct, I don't see it anymore with the current master.
Closing.
Actions