Libev leaks memory

Brandon Black blblack at gmail.com
Thu May 15 15:40:08 CEST 2008


hsanson wrote:
> 
> I am using libev to implement a media server and so far everything is 
> smooth and easy. The only problem that I found is that libev seems to 
> leak memory.

[...]

> ==30474== 256 bytes in 1 blocks are still reachable in loss record 1 of 1
> ==30474==    at 0x4022AB8: malloc (vg_replace_malloc.c:207)
> ==30474==    by 0x4022BFC: realloc (vg_replace_malloc.c:429)
> ==30474==    by 0x4041357: ev_realloc_emul (ev.c:377)
> ==30474==    by 0x40429B1: array_realloc (ev.c:394)
> ==30474==    by 0x404408B: ev_signal_start (ev.c:2118)
> ==30474==    by 0x4044170: ev_default_loop_init (ev.c:1485)
> ==30474==    by 0x8049660: ev_default_loop (ev.h:433)
> ==30474==    by 0x8049630: main (video_server.c:9)
> ==30474==

[...]

I wouldn't worry about it too much.  Those 256 bytes are "leaked" just 
once, so it's not a real leak, it's more like "necessary memory that 
can't be easily free()'d up at exit".

-- Brandon



More information about the libev mailing list