Re: [Evolution-hackers] [Fwd: [Fwd: A problem in libsoup]]
- From: Dan Winship <danw ximian com>
- To: Joe Shaw <joe ximian com>
- Cc: evolution-hackers lists ximian com
- Subject: Re: [Evolution-hackers] [Fwd: [Fwd: A problem in libsoup]]
- Date: 09 Apr 2003 12:00:44 -0400
On Tue, 2003-04-08 at 11:36, Joe Shaw wrote:
> On Mon, 2003-04-07 at 23:10, Sean Gao wrote:
> > Hi Dan,
> > We just check out the libsoup head again and find that Joe's patch
> > has been reverted. This looks fine for us.
> > Thanks a lot.
> The revert is just a temporary workaround. My patch has to go back in
> for rcd, so it's worth finding the crash with it in. Unfortunately, I
> don't see it with rcd... does it only happen with NTLM?
No, it's not NTLM-related at all it turns out. It only happens with
openssl, and it happens pretty reliably then. I think the issue is that
with non-ssl or non-openssl, soup doesn't notice when the connection is
closed until after it has finished processing the response, but in the
openssl case, because of the interaction with the proxy, it notices
right away (and so connection_death gets called before soup has
processed any of the response, and some of the response-processing code
assumes the message is attached to a valid connection).
Having just spent a lot of time looking at this, I'm less and less
convinced that connection_death() was wrong to begin with. I think the
problem rcd is seeing is actually caused by something leaving
conn->in_use set TRUE when nothing is actually paying attention to the
] [Thread Prev