Memcached crashing on FreeBSD

Anatoly Vorobey mellon at
Mon Apr 11 09:31:30 PDT 2005

On Mon, Apr 11, 2005 at 12:01:56PM -0400, Jason Coene wrote:
> Hey Guys,
> We have a winner - backtrace below, here's what it sent to screen:
> memcached in malloc(): error: allocation failed
> Abort trap (core dumped)

> #1  0x280ba7f8 in raise () from /lib/
> #2  0x28132f02 in abort () from /lib/
> #3  0x2813167e in tcflow () from /lib/
> #4  0x28131f1b in tcflow () from /lib/
> #5  0x281322d6 in malloc () from /lib/

Check your /etc/malloc.conf ; does it have "A" in it?

> #6  0x0804b56d in slabs_newslab (id=5) at slabs.c:111

It's normal for memcache to fail to allocate a new slab with
malloc(); in this case malloc() should just return an error, but
it aborts on your system, probably due to your configuration of
/etc/malloc.conf . See malloc(3). You can try running memcached
with MALLOC_OPTIONS set to "a"; that should override your 
/etc/malloc.conf settings if that's the problem.

Alternatively, memcached could trap and ignore SIGABRT on FreeBSD;
not sure how good an idea that is, opinions?

"There's nothing simply good, nor ill alone" -- John Donne

More information about the memcached mailing list