zhixinwen opened a new issue, #3097: URL: https://github.com/apache/kvrocks/issues/3097
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/kvrocks/issues) and found no similar issues. ### Version We were running on test with `2.12.1` + https://github.com/apache/kvrocks/pull/3047 + https://github.com/apache/kvrocks/pull/3061 ``` E20250803 15:00:48.854673 139623678342720 signal_util.h:33] Ooops! Apache Kvrocks version 2.12.1 (commit 034f1c9c) got signal: Segmentation fault (11) E20250803 15:00:49.486161 139623678342720 signal_util.h:35] Stack trace (most recent call first): #0 0x0000562b57c640b0 in SegvHandler at /root/kvrocks/kvrocks/build/kvrocks #1 0x00007efcb41b151f in __sigaction at /lib/x86_64-linux-gnu/libc.so.6 #2 0x0000562b586912c5 in evbuffer_add at /root/kvrocks/kvrocks/build/kvrocks #3 0x0000562b57f4fe2a in FeedSlaveThread::readCallback(bufferevent*, void*) [clone .constprop.0] at /root/kvrocks/kvrocks/build/kvrocks #4 0x0000562b5869acc1 in bufferevent_run_deferred_callbacks_unlocked at bufferevent.c #5 0x0000562b586a32c3 in event_process_active_single_queue at event.c #6 0x0000562b586a39be in event_process_active at event.c #7 0x0000562b586a582f in event_base_loop.constprop.0 at event.c #8 0x0000562b57eaadcd in std::thread::_State_impl<std::thread::_Invoker<std::tuple<util::CreateThread<WorkerThread::Start()::{lambda()#1}>(char const*, WorkerThread::Start()::{lambda()#1})::{lambda()#1}> > >::_M_run() at /root/kvrocks/kvrocks/build/kvrocks #9 0x0000562b588bbe03 in execute_native_thread_routine at thread.o #10 0x00007efcb4203ac2 in pthread_condattr_setpshared at /lib/x86_64-linux-gnu/libc.so.6 #11 0x00007efcb429584f in __xmknodat at /lib/x86_64-linux-gnu/libc.so.6 E20250803 15:00:49.486265 139623678342720 signal_util.h:36] It would be greatly appreciated if you could submit this crash to https://github.com/apache/kvrocks/issues along with the stacktrace above, logs and any relevant information. Segmentation fault ``` I will debug this. ### Minimal reproduce step call `SET+WAIT` continuously for a long time like 6 hours ### What did you expect to see? no segfault ### What did you see instead? segfault ### Anything Else? _No response_ ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
