Bugs item #2891591, was opened at 2009-11-04 01:56
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2891591&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: http
Group: bad behaviour
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Constantine Sapuntzakis (csapuntz)
Assigned to: Daniel Stenberg (bagder)
Summary: Curl_dns_entry leaked on redirect + connect failure

Initial Comment:
How to repro:

  1. Set up a first web server that redirects (307) to a http://server:port that's down
  2. Have curl connect to the first web server using curl multi

After the curl_easy_cleanup call, there will be curl dns entries hanging around with in_use != 0.

Working on a patch...

----------------------------------------------------------------------

>Comment By: Daniel Stenberg (bagder)
Date: 2009-11-14 09:45

Message:
When applied, test 19 fails with a memory leak (if configure --enable-debug
was used):

test 019...[attempt connect to non-listening socket]

** MEMORY FAILURE
Leak detected: memory still allocated: 60 bytes
At 836e2e4, there's 16 bytes.
 allocated by curl_addrinfo.c:156
At 836e2b4, there's 32 bytes.
 allocated by curl_addrinfo.c:137
At 836e384, there's 12 bytes.
 allocated by hostip.c:344

 - abort tests

----------------------------------------------------------------------

Comment By: Constantine Sapuntzakis (csapuntz)
Date: 2009-11-12 01:33

Message:
And for what it's worth, the patch fixes test cases 311 and 312 which now
have memory leaks because of recent DNS hostcache behavior change.

----------------------------------------------------------------------

Comment By: Constantine Sapuntzakis (csapuntz)
Date: 2009-11-11 18:19

Message:
New patch attached.

Clean up in Curl_disconnect. Along with plugging the DNS ref leak in
multi.c, this allows us to simplify Curl_connect too.

----------------------------------------------------------------------

Comment By: Constantine Sapuntzakis (csapuntz)
Date: 2009-11-04 03:16

Message:
disconnet_conn = true in multi_runsingle but Curl_done is not always called
- which would clean up the conn->dns_entry. Don't know if it's safe to call
Curl_done so instead I cleanup in disconnect_conn clause no matter what.

Also, maintain invariant in ConnectPlease that if it returns an error then
conn->dns_entry == NULL to avoid double unlocks.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=2891591&group_id=976
Received on 2009-11-14