This time it crashed when I call FT.EXPLAIN command of redisearch in v.0.9.6. But it didn't crash at startup like before.
=== KEYDB BUG REPORT START: Cut & paste starting from here ===
7:S 26 Jul 2019 08:57:21.318 # === ASSERTION FAILED ===
7:S 26 Jul 2019 08:57:21.318 # ==> multi.cpp:296 'GlobalLocksAcquired()' is not true
7:S 26 Jul 2019 08:57:21.318 # (forcing SIGSEGV to print the bug report.)
7:S 26 Jul 2019 08:57:21.318 # KeyDB 0.9.6 crashed by signal: 11
7:S 26 Jul 2019 08:57:21.318 # Crashed running the instruction at: 0x55aced61926e
7:S 26 Jul 2019 08:57:21.318 # Accessing address: 0xffffffffffffffff
7:S 26 Jul 2019 08:57:21.318 # Failed assertion: GlobalLocksAcquired() (multi.cpp:296)
------ STACK TRACE ------
EIP:
keydb-server *:6379(_serverAssert+0x7e) [0x55aced61926e]
Backtrace:
keydb-server *:6379(logStackTrace(ucontext_t*)+0x6b) [0x55aced61c25b]
keydb-server *:6379(sigsegvHandler(int, siginfo_t*, void*)+0xbf) [0x55aced61c9ef]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7fc625d61890]
keydb-server *:6379(_serverAssert+0x7e) [0x55aced61926e]
keydb-server *:6379(touchWatchedKey(redisDb*, redisObject*)+0x71) [0x55aced618cf1]
keydb-server *:6379(RM_CloseKey(RedisModuleKey*)+0x75) [0x55aced64b125]
keydb-server *:6379(+0xc7646) [0x55aced64c646]
keydb-server *:6379(moduleFreeContext(RedisModuleCtx*)+0x9b) [0x55aced64c76b]
keydb-server *:6379(RM_FreeThreadSafeContext(RedisModuleCtx*)+0x9) [0x55aced64c809]
/data/redisearch.so(+0x42140) [0x7fc622b05140]
/data/redisearch.so(+0xadabe) [0x7fc622b70abe]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x76db) [0x7fc625d566db]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7fc625a7f88f]
------ INFO OUTPUT ------
7:S 26 Jul 2019 08:57:21.318 # === ASSERTION FAILED ===
7:S 26 Jul 2019 08:57:21.318 # ==> object.cpp:961 'GlobalLocksAcquired()' is not true
7:S 26 Jul 2019 08:57:21.318 # (forcing SIGSEGV to print the bug report.)
bash: line 1: 7 Segmentation fault (core dumped) keydb-server /conf/redis.conf --loadmodule /data/redisearch.so TIMEOUT 0 ON_TIMEOUT fail 2> >(tee -a /data/redis.log >&2)
Originally posted by @oruchreis in #68 (comment)
This time it crashed when I call FT.EXPLAIN command of redisearch in v.0.9.6. But it didn't crash at startup like before.
Originally posted by @oruchreis in #68 (comment)