Re: [Libevent-users] deadlock in libevent-2.0.5-beta

2010-07-02 Thread Zhou Li
I met such deadlock too. It happened under very high load just as you said. I think the cause is that the call write(th_notify_fd[1]) got blocked ( sorry I didn't remember the exact position of this call to write th_notify_fd). In event.c line 2597: /* This can't be right, can it? We w

Re: [Libevent-users] deadlock in libevent-2.0.5-beta

2010-07-02 Thread Nick Mathewson
On Thu, Jul 1, 2010 at 6:44 AM, Avi Bab wrote: > > > Running on Linux with pthreads. > > > > One thread (CBTcpProxyListenerThread below) adds bufferevents (with option > BEV_OPT_THREADSAFE) to an event_base. > > A second thread (CBTcpProxySenderThread) dispatches on the event_base. > > > > buffere

Re: [Libevent-users] deadlock in libevent-2.0.5-beta

2010-07-02 Thread Joachim Bauch
Hi, On 01.07.2010 12:44, Avi Bab wrote: Running on Linux with pthreads. One thread (CBTcpProxyListenerThread below) adds bufferevents (with option BEV_OPT_THREADSAFE) to an event_base. A second thread (CBTcpProxySenderThread) dispatches on the event_base. have you tried creating your buffere