Menu ▾ ▴

#1175 Memory leak with CURL_RESOLVE and manual removal of easy handle from multi

closed-fixed
Daniel Stenberg
memory leak (5)
5
2013-06-21
2012-12-18
Benbuck Nason
No

There is a DNS leak in the curl 7.28.1 (and probably earlier) similar to the one that was fixed for that release. Basically if you use CURLOPT_RESOLVE on an easy handle and then manually remove it from the multi, curl_multi_cleanup() will then not call Curl_hostcache_clean() to free the added DNS entries. Reproduction case attached.

1 Attachments
curl_dns_leak.c

Discussion

  • Daniel Stenberg

    Daniel Stenberg - 2012-12-18
    • labels: --> memory leak
    • assigned_to: Daniel Stenberg
    • milestone: -->
     

  • Daniel Stenberg

    Daniel Stenberg - 2012-12-21
    • status: open --> open-confirmed
     

  • Daniel Stenberg

    Daniel Stenberg - 2012-12-21

    Thanks for the report!

    I've been able to repeat it. Next I'll turn it into a test case and see what I can do to fix it...

     

  • Daniel Stenberg

    Daniel Stenberg - 2013-02-11
    • status: open-confirmed --> closed-fixed
     

  • Daniel Stenberg

    Daniel Stenberg - 2013-02-11

    This problem doesn't exist anymore in 7.29.0. Closing as fixed.

     
MongoDB Logo MongoDB