Re: Leak when destination not reachable
Date: Fri, 22 Jun 2007 20:14:37 +0530
I've migrated my sources to new version of curl(7.16.2).
But I'm still observing the leak. This time I'm not able to produce the
leak trace file.
Following are the observations/scenarios:
- I'm using curl_multi_perform call to do HTTP posts.
- Server is set to be 'not reachable'.
- If my URL has host name(e.g. google.com) then it leaks.
- If I replace host name with the ip address then it does not leak.
If URL is 'reachable' then in both the cases(hostname or ip address) it
does not leak.
FYI, In last version of curl(7.15.1) I found this leak in
Any inputs are welcome.
On Mon, 2007-06-18 at 19:27 +0200, Daniel Stenberg wrote:
> On Mon, 18 Jun 2007, vikram wrote:
> > I'm using curl version 7.15.1
> > Any details on this issue are welcome. Also I'm interested to know if this
> > issue has been resolved in the latest version of curl.
> Get 7.16.2 and try your code with it and you'll soon know. 7.15.1 is ancient
> and we've fixed hundreds of bugs since then and I would say it is likely that
> we fixed the bug you mention here as well.
Received on 2007-06-22