On Sun, Jan 23, 2011 at 3:59 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 23.01.2011 14:41, Lieven Govaerts wrote:
>
>>
>>
>> On Fri, Jan 21, 2011 at 7:59 AM, Justin Erenkrantz
>> <justin_at_erenkrantz.com <mailto:justin_at_erenkrantz.com>> wrote:
>>
>> On Thu, Jan 20, 2011 at 3:18 PM, Lieven Govaerts <svnlgo_at_mobsol.be
>> <mailto:svnlgo_at_mobsol.be>> wrote:
>> >> Greg or Lieven, any thoughts here? -- justin
>> >
>> > At least the one rev that fixes this issue, don't know if the
>> other are
>> > already working in all scenario's.
>> > I'll look at it this weekend and make a release.
>>
>> Woohoo. Thanks. I'll be sure to test it. Let me know if you need
>> any help. -- justin
>>
>>
>> I've prepared branch 0.7.x with the changes that are safe to go in serf
>> 0.7.1.
>>
>> I'm running some tests on Linux, Windows 7 and Mac Os X. On the latter
>> svn trunk currently doesn't build for me (is_atomicity_error symbol not
>> found), but doesn't seem to be related to serf.
>>
>> I'd appreciate some more testing, before I make the release later this
>> week. The code to get is:
>> http://serf.googlecode.com/svn/branches/0.7.x at r1427.
>>
>
> I've used a build from serf trunk for a while now without problems.
> The serf log indicates that r1416 has been merged, but r1417 has not. Is
> there a reason why this memory leak fix hasn't been merged to 0.7.x?
r1417 is part of a refactoring on trunk to move the connection related code
in a separate bucket (httpconn). I doubt that that code is really stable
yet, so I'd rather not merge it to 0.7.x.
Lieven
Received on 2011-01-23 16:10:19 CET