Project

General

Profile

Actions

Bug #5184

closed

possible memleak: "Indirect leak of 44688 byte(s) in 342 object(s) allocated from [...] _talloc_zero"

Added by neels 6 months ago. Updated 5 months ago.

Status:
Closed
Priority:
High
Assignee:
-
Target version:
-
Start date:
06/16/2021
Due date:
% Done:

0%

Spec Reference:

Description

running ttcn3-bsc-tests locally, osmo-stp compiled with asan, when I ctrl-c osmo-stp after a while, i often get:

=================================================================
==2538==ERROR: LeakSanitizer: detected memory leaks

Indirect leak of 44688 byte(s) in 342 object(s) allocated from:
    #0 0x7fbb4d20d330 in __interceptor_malloc (/lib/x86_64-linux-gnu/libasan.so.5+0xe9330)
    #1 0x7fbb4cdc7140 in _talloc_zero (/lib/x86_64-linux-gnu/libtalloc.so.2+0x9140)

Related issues

Related to OsmoSTP - Bug #5185: possible memleak: "Indirect leak of 22800 byte(s) in 228 object(s) allocated from [...] _talloc_memdup"ClosedHoernchen06/16/2021

Actions
Actions #1

Updated by neels 6 months ago

  • Related to Bug #5185: possible memleak: "Indirect leak of 22800 byte(s) in 228 object(s) allocated from [...] _talloc_memdup" added
Actions #2

Updated by neels 6 months ago

here the output of another instance of this leak:

=================================================================
==2673==ERROR: LeakSanitizer: detected memory leaks

Indirect leak of 70560 byte(s) in 540 object(s) allocated from:
    #0 0x7f3493add330 in __interceptor_malloc (/lib/x86_64-linux-gnu/libasan.so.5+0xe9330)
    #1 0x7f3493696140 in _talloc_zero (/lib/x86_64-linux-gnu/libtalloc.so.2+0x9140)

The fact that the numbers are different for differing running time seems to confirm that this is an actual leak.

Actions #3

Updated by neels 6 months ago

see also comment 3 and 4 in #5185

Actions #4

Updated by Hoernchen 5 months ago

  • Status changed from New to Closed

Also presumed to be fixed by related bug.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)