Hello; Here is the stack trace: (on out of memory)

348:M 26 Nov 15:26:17.047 # Can't save in background: fork: Cannot allocate memory 348:M 26 Nov 15:26:46.734 * 1 changes in 900 seconds. Saving... 348:M 26 Nov 15:26:46.734 # Can't save in background: fork: Cannot allocate memory 348:M 26 Nov 15:27:22.650 * 1 changes in 900 seconds. Saving... 348:M 26 Nov 15:27:22.651 # Can't save in background: fork: Cannot allocate memory 348:M 26 Nov 15:27:30.123 * 1 changes in 900 seconds. Saving... 348:M 26 Nov 15:27:30.123 # Can't save in background: fork: Cannot allocate memory 348:M 26 Nov 15:27:36.033 * 1 changes in 900 seconds. Saving... 348:M 26 Nov 15:27:36.034 # Can't save in background: fork: Cannot allocate memory 348:M 26 Nov 15:27:42.099 * 1 changes in 900 seconds. Saving... 348:M 26 Nov 15:27:42.099 # Can't save in background: fork: Cannot allocate memory 348:M 26 Nov 15:27:48.067 * 1 changes in 900 seconds. Saving... 348:M 26 Nov 15:27:48.067 # Can't save in background: fork: Cannot allocate memory 348:M 26 Nov 15:27:52.733 # Out Of Memory allocating 29998 bytes!

=== REDIS BUG REPORT START: Cut & paste starting from here === 348:M 26 Nov 15:27:52.749 # ------------------------------------------------ 348:M 26 Nov 15:27:52.749 # !!! Software Failure. Press left mouse button to continue 348:M 26 Nov 15:27:52.749 # Guru Meditation: Redis aborting for OUT OF MEMORY #server.c:3589 348:M 26 Nov 15:27:52.749 # (forcing SIGSEGV in order to print the stack trace) 348:M 26 Nov 15:27:52.749 # ------------------------------------------------ 348:M 26 Nov 15:27:52.749 # Redis 4.0.9 crashed by signal: 11 348:M 26 Nov 15:27:52.749 # Crashed running the instruction at: 0x466fb7 348:M 26 Nov 15:27:52.749 # Accessing address: 0xffffffffffffffff 348:M 26 Nov 15:27:52.749 # Failed assertion: (:0)

------ STACK TRACE ------ EIP: /usr/local/bin/redis-server *:6379(_serverPanic+0x117)[0x466fb7]

Comment From: trevor211

It's reasonable that redis got killed if run out of memory.

Comment From: oranagra

for the record, it wasn't killed (OOM kill by the kernel is done with SIGKILL, and doesn't leave traces in the log file). Here redis committed suicide when it failed to allocate 29 kilobytes.

@w0dm4n can you provide the complete crash log, and possibly even more of the logs from before the crash? can you describe what you did, and maybe how to reproduce?

Comment From: w0dm4n

Hey, sorry 2yr after this occurs is kinda late for any logs, but the only thing that i can tell you is that it was a prod server running out just basically normally with a lot of execution on search key and get/mget, then something, maybe a big request or a third party consumed the entire available vm memory, once it went out of memory redis went pretty bad at handling this case and ended up with a segv