Re: [asio-users] deadlock when handler destructor causes close()

[Arvid N. <c9...@cs...>]

On Jan 25, 2006, at 07:54, Christopher Kohlhoff wrote:

> Hi Arvid,
>
> --- Arvid Norberg <c9...@cs...> wrote:
>> I'm now experiencing a deadlock with the cvs version of asio
>> (from a few days ago). It occurs when I have one connection
>> receiving data  continously and another connection that is
>> closed. The connection  that is being closed will cause the
>> deadlock because the last  shared_ptr to the connection object
>> (which in turn is holding the  tcp::socket) is stored in the
>> handler. When the handler is destructed the socket will be
>> destructed and closed, and close will lock the  demuxer
>> service, and deadlock.
>
> I think I know what the problem is, and I have just committed a
> change to CVS to try to fix it. Can you please give it a go and
> see what happens. It should show up in the public sourceforge
> CVS in about 6 hours.
>
> I'm planning to rewrite the reactor stuff soon anyway to
> eliminate memory allocations, reduce locking time, and generally
> improve performance. The kqueue_reactor will be the first to be
> rewritten, as I'm using Mac OS X as my main dev platform.

Ok, great! I will try this as soon as possible. I'll be out of town  
for the next 3 weeks, so no sooner than that.

--
Arvid Norberg