[systemd-devel] Leak mempool/hashmap
Jan Janssen
medhefgo at web.de
Thu Nov 6 10:59:15 PST 2014
On 2014-11-06 19:05, Lennart Poettering wrote:
> On Thu, 06.11.14 18:36, Jan Janssen (medhefgo at web.de) wrote:
>
>> Hi,
>>
>> I just noticed that mempool/hashmap leaks memory. It's as simple as this to
>> trigger:
>>
>> #include "hashmap.h"
>> int main(int argc, const char *argv[]) {
>> Hashmap *m = hashmap_new(&string_hash_ops);
>> hashmap_free(m);
>> }
>
> How did you determine the leak?
>
> Note that the hashmap uses an allocation cache. It's not freed on
> shutdown, but it's not leaked either...
>
> Lennart
>
I've noticed while testing my cryptsetup-generator rewrite with
valgrind. It's still reachable according to valgrind, but a silent
output would be nice to have.
Jan
More information about the systemd-devel
mailing list