Re: [Libevent-users] Memory leak in locks?

[Tomer Heber <tomer@xxxxxxxxxxxx>]

Hi,

Have a look at the end of section R1 in the libevent reference manual.

There is a function to release globally allocated memory. However, it's available only in newer versions.

Sent from my LG Mobile

------ Original message------

From: Ralph Castain

Date: Fri, Jan 9, 2015 20:06

To: libevent-users@xxxxxxxxxxxxx;

Subject:[Libevent-users] Memory leak in locks?

Hi folks

I’ve trying to make a new library that uses libevent be valgrind clean. This is a threaded library, and so libevent is thread enabled. I create a new event base, and I call event_base_free before finalizing.

However, I keep seeing reports like this:

==16029== 40 bytes in 1 blocks are still reachable in loss record 1 of 3
==16029==    at 0x4C288FE: malloc (in /home/common/local/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==16029==    by 0x52A9EE1: evthread_posix_lock_alloc (evthread_pthread.c:46)
==16029==    by 0x5075572: event_global_setup_locks_ (event.c:2900)
==16029==    by 0x52AA08A: evthread_use_pthreads (evthread_pthread.c:185)

This is with libevent 2.0.22-stable. Is this an expected situation? Or is there something I need to do beyond event_base_free to get a clean finalize?

Thanks
Ralph

***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.