multi: fix memory leak when stopped during name resolve

When the application just started the transfer and then stops it while
the name resolve in the background thread hasn't completed, we need to
wait for the resolve to complete and then cleanup data accordingly.

Enabled test 1553 again and added test 1590 to also check when the host
name resolves successfully.

Detected by OSS-fuzz.
Closes #1968
This commit is contained in:
Daniel Stenberg 2018-06-14 16:28:59 +02:00
parent 676f4b742d
commit ac9a179fe9
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2
7 changed files with 97 additions and 24 deletions

View file

@ -18,5 +18,3 @@
1510
# Pipelining test that is causing false positives a little too often
1903
# causes memory leaks for now:
1553