Hello Christopher, Thank you for the quick answer and the patch.
On Wed, Jun 20, 2018 at 11:32 AM Christopher Faulet <cfau...@haproxy.com> wrote: > Here is a patch to avoid a thread to exit its polling loop while others > are waiting in the sync point. It is a theoretical patch because I was > not able to reproduce the bug. > Could you check if it fixes it please ? Unfortunately, it does not fix the issue; I am getting the same backtrace: #0 0x000055f30960a10b in thread_sync_barrier (barrier=0x55f309875528 <barrier.27101>) at src/hathreads.c:114 #1 thread_enter_sync () at src/hathreads.c:127 #2 0x000055f3095b27a2 in sync_poll_loop () at src/haproxy.c:2376 #3 run_poll_loop () at src/haproxy.c:2433 #4 run_thread_poll_loop (data=data@entry=0x55f31c4b0c50) at src/haproxy.c:2463 #5 0x000055f30952e856 in main (argc=<optimized out>, argv=<optimized out>) at src/haproxy.c:3065 however the backtrace is different on some machines: #0 0x00007f31fd89ff57 in pthread_join () from /lib64/libpthread.so.0 #1 0x000055e184a5486a in main (argc=<optimized out>, argv=<optimized out>) at src/haproxy.c:3069 -- William
