Closed doyoubi closed 4 years ago
@doyoubi Thank you, I will investigate on this.
@doyoubi I cannot reproduce the issue, I've tried your steps many times but always without problems.
The OS is Mac OSX. The backend Redis cluster is just a single node with all the slots:
127.0.0.1:8899> cluster nodes
eb1adebbd80b6d6ce7c6a5e37f4f040b2dbe138b :8899@18899 myself,master - 0 0 0 connected 0-16383
The last MGET will block. Then press ctrl-c to trigger crash.
Does the traceback help?
* thread #2, stop reason = EXC_BAD_ACCESS (code=EXC_I386_GPFLT)
* frame #0: 0x00000001000015c5 redis-cluster-proxy`listNext(iter=0x000070000d1ade20) at adlist.c:0
frame #1: 0x0000000100012618 redis-cluster-proxy`freeClient [inlined] freeAllClientRequests(c=<unavailable>) at proxy.c:2737:18
frame #2: 0x0000000100012524 redis-cluster-proxy`freeClient(c=0x0000000100501790) at proxy.c:2780
frame #3: 0x0000000100002328 redis-cluster-proxy`aeProcessEvents(eventLoop=0x00000001004018f0, flags=11) at ae.c:451:17
frame #4: 0x000000010000266b redis-cluster-proxy`aeMain(eventLoop=0x00000001004018f0) at ae.c:521:9
frame #5: 0x0000000100018914 redis-cluster-proxy`execProxyThread(ptr=0x00000001004011a0) at proxy.c:4771:5
frame #6: 0x00007fff7448c2eb libsystem_pthread.dylib`_pthread_body + 126
frame #7: 0x00007fff7448f249 libsystem_pthread.dylib`_pthread_start + 66
frame #8: 0x00007fff7448b40d libsystem_pthread.dylib`thread_start + 13
@doyoubi Ok, I've been able to replicate it. Now I'm working to fix it. Thank you very much!
@doyoubi Fixed in 9a2383d
Version
unstable branch commit 6751bf515fcef0a46c273f0199e49794592529ec
Steps to Reproduce
Crash Log: