memory leak #24

Closed
ferlatum opened this Issue Mar 26, 2013 · 2 comments

Projects

None yet

2 participants

@ferlatum

It seems that there is still a memory leak.
I run Twemcache under Valgrind, and submitted many small objects (a sequence of set/get of object with key "i" and random value, with i = 1, 2, 3, ...).
The memory keeps growing.
The output of Valgrind says that, when a suffix is created, the sequence of calls are
asc_respond_get (mc_ascii.c) -> asc_create_suffix (mc_ascii.c) -> cache_alloc (mc_cache.c)
but the created memory is not properly freed or managed (blocks are definitely lost).

Could you please check?

@thinkingfish thinkingfish was assigned Apr 6, 2013
@thinkingfish
Member

I'll take a look tomorrow and get back to you.

@thinkingfish
Member

Will be fixed in Twemcache 2.6.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment