Re: [libextractor] is this memory leak in libextractor?

[Christian Grothoff]

This is libltdl.  In good news, AFAIK it only occurs once during initialization,
so it's not a big leak.

Christian

Zitat von Sergey 'Jin' Bostandzhyan <address@hidden>:
> Hi,
>
> I am using libextractor in my application to read some metadata, I am
> using EXTRACTOR_freeKeywords() and EXTRACTOR_removeAll() functions after,
> so I am not forgetting to free anything.
>
> I am not so experienced with valgrind, but I figure that this is indicating
> a leak:
>
> ==20962== 1618 bytes in 77 blocks are definitely lost in loss record 9 of 9
> ==20962==    at 0x1B903228: malloc (vg_replace_malloc.c:130)
> ==20962==    by 0x8EA567: (within /usr/lib/libltdl.so.3.1.0)
> ==20962==    by 0x8EB0C8: (within /usr/lib/libltdl.so.3.1.0)
> ==20962==    by 0x8ED388: (within /usr/lib/libltdl.so.3.1.0)
> ==20962==    by 0x8ED5CF: lt_dladdsearchdir (in /usr/lib/libltdl.so.3.1.0)
> ==20962==    by 0x1B91C8D7: le_ltdl_init (in /usr/lib/libextractor.so.1.0.0)
> ==20962==    by 0x1B91D950: (within /usr/lib/libextractor.so.1.0.0)
> ==20962==    by 0x1B91C400: (within /usr/lib/libextractor.so.1.0.0)
> ==20962==    by 0x1B8F02A7: _dl_init (in /lib/ld-2.3.5.so)
> ==20962==    by 0x1B8E47FE: (within /lib/ld-2.3.5.so)
>
> In this case I was using the libextractor_jpeg library, it gets much worse
> when I load all default libraries.
>
> Is the problem in libextractor, or is it libltdl's fault?
>
> I am using the libtool-libs-1.5.6-4.FC3.2 package, problem is reproducible
> with
> libextractor 0.4.2 as well as libextractor 0.5.2
>
> Kind regards,
> Jin
>
>
> _______________________________________________
> libextractor mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/libextractor
>