Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 294 by [email protected]: segfault under low memory conditions
http://code.google.com/p/memcached/issues/detail?id=294
Under certain low memory conditions, memcached can segfault. I cannot
reproduce this manually, but it's occurred in production a couple times now.
gdb stack from the core dump:
Core was generated by `/usr/local/memcached/bin/memcached -r -m 15500 -p
11211 -c 10000 -o slab_reassi'.
Program terminated with signal 11, Segmentation fault.
#0 dispatch_conn_new (sfd=2007, init_state=conn_new_cmd, event_flags=18,
read_buffer_size=2048, transport=tcp_transport) at thread.c:355
355 thread.c: No such file or directory.
in thread.c
(gdb) where
#0 dispatch_conn_new (sfd=2007, init_state=conn_new_cmd, event_flags=18,
read_buffer_size=2048, transport=tcp_transport) at thread.c:355
#1 0x0000000000408637 in drive_machine (fd=<value optimized out>,
which=<value optimized out>, arg=0x1c86c90) at memcached.c:3787
#2 event_handler (fd=<value optimized out>, which=<value optimized out>,
arg=0x1c86c90) at memcached.c:4067
#3 0x00007f6e3de0f194 in event_base_loop () from /usr/lib/libevent-1.4.so.2
#4 0x000000000040b949 in main (argc=<value optimized out>, argv=<value
optimized out>) at memcached.c:5230
memcached version: 1.4.14
started with command: /usr/local/memcached/bin/memcached -r -m 15500 -p
11211 -c 10000 -o slab_reassign slab_automove -d
OS: Linux 2.6.38-13-virtual #52-Ubuntu SMP x86_64 GNU/Linux
