Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Torture test 530 fails on mac #8129

Closed
bagder opened this issue Dec 9, 2021 · 0 comments · Fixed by #8131
Closed

Torture test 530 fails on mac #8129

bagder opened this issue Dec 9, 2021 · 0 comments · Fixed by #8131

Comments

@bagder
Copy link
Member

@bagder bagder commented Dec 9, 2021

The failure is reproducible for me on mac, I can't make it happen on Linux. (The exact iteration that fails isn't always 250)

$ ./runtests.pl -t 530
********* System characteristics ******** 
* curl 7.81.0-DEV (x86_64-apple-darwin20.6.0) 
* libcurl/7.81.0-DEV (SecureTransport) OpenSSL/3.0.0 zlib/1.2.11 brotli/1.0.9 zstd/1.5.0 c-ares/1.18.1 libidn2/2.3.2 nghttp2/1.46.0 librtmp/2.3
* Features: alt-svc AsynchDNS brotli Debug HSTS HTTP2 HTTPS-proxy IDN IPv6 Largefile libz MultiSSL NTLM NTLM_WB SSL TLS-SRP TrackMemory UnixSockets zstd
* Disabled: 
* Host: Daniels-mini2
* System: Darwin Daniels-mini2 21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64 x86_64
* OS: darwin
* Servers: HTTP-IPv6 HTTP-unix FTP-IPv6 
* Env: 
* Seed: 208179
***************************************** 
test 0530...[multi_socket interface transfer with callbacks returning error]
 251 functions to make fail
** MEMORY FAILURE
Leak detected: memory still allocated: 416 bytes
At 7fb0749048e8, there's 416 bytes.
 allocated by hash.c:73
LIMIT dynbuf.c:98 realloc reached memlimit
 Failed on function number 250 in test.
 invoke with "-t250" to repeat this single case.

 - abort tests
TESTDONE: 1 tests were considered during 17 seconds.
TESTDONE: 0 tests out of 1 reported OK: 0%

TESTFAIL: These test cases failed: 530 

bagder added a commit that referenced this issue Dec 10, 2021
Since each socket hash entry may themselves have a hash table in them,
the destroying of the socket hash needs to make sure all the subhashes
are also correctly destroyed to avoid leaking memory.

Fixes #8129
@bagder bagder closed this in e43ad4b Dec 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

1 participant