```2023-12-09 17:33:02 I chat: ZenCZ: nooo ==20414== Thread 6: ==20414== Invalid read of size 8 ==20414== at 0x7D17F3C: destroy_async_data.lto_priv.0 (asyn-thread.c:376) ==20414== by 0x7D71273: UnknownInlinedFun (asyn-thread.c:139) ==20414== by 0x7D71273: Curl_disconnect (url.c:666) ==20414== by 0x7D510E2: UnknownInlinedFun (conncache.c:400) ==20414== by 0x7D510E2: multi_done.lto_priv.0 (multi.c:776) ==20414== by 0x7D5C533: multi_runsingle (multi.c:2536) ==20414== by 0x7D5ECB5: curl_multi_perform (multi.c:2702) ==20414== by 0x7D2EDC3: UnknownInlinedFun (easy.c:671) ==20414== by 0x7D2EDC3: UnknownInlinedFun (easy.c:761) ==20414== by 0x7D2EDC3: curl_easy_perform (easy.c:780) ==20414== by 0x18D0B3: ??? (in /usr/bin/DDNet) ==20414== by 0x18D25B: ??? (in /usr/bin/DDNet) ==20414== by 0x191109: ??? (in /usr/bin/DDNet) ==20414== by 0x1AF23B: ??? (in /usr/bin/DDNet) ==20414== by 0x83379EA: start_thread (pthread_create.c:444) ==20414== by 0x83BB653: clone (clone.S:100) ==20414== Address 0x68 is not stack'd, malloc'd or (recently) free'd ==20414== ==20414== ==20414== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==20414== Access not within mapped region at address 0x68 ==20414== at 0x7D17F3C: destroy_async_data.lto_priv.0 (asyn-thread.c:376) ==20414== by 0x7D71273: UnknownInlinedFun (asyn-thread.c:139) ==20414== by 0x7D71273: Curl_disconnect (url.c:666) ==20414== by 0x7D510E2: UnknownInlinedFun (conncache.c:400) ==20414== by 0x7D510E2: multi_done.lto_priv.0 (multi.c:776) ==20414== by 0x7D5C533: multi_runsingle (multi.c:2536) ==20414== by 0x7D5ECB5: curl_multi_perform (multi.c:2702) ==20414== by 0x7D2EDC3: UnknownInlinedFun (easy.c:671) ==20414== by 0x7D2EDC3: UnknownInlinedFun (easy.c:761) ==20414== by 0x7D2EDC3: curl_easy_perform (easy.c:780) ==20414== by 0x18D0B3: ??? (in /usr/bin/DDNet) ==20414== by 0x18D25B: ??? (in /usr/bin/DDNet) ==20414== by 0x191109: ??? (in /usr/bin/DDNet) ==20414== by 0x1AF23B: ??? (in /usr/bin/DDNet) ==20414== by 0x83379EA: start_thread (pthread_create.c:444) ==20414== by 0x83BB653: clone (clone.S:100) ==20414== If you believe this happened as a result of a stack ==20414== overflow in your program's main thread (unlikely but ==20414== possible), you can try to increase the size of the ==20414== main thread stack using the --main-stacksize= flag. ==20414== The main thread stack size used in this run was 8388608. ^C==20414== ==20414== HEAP SUMMARY: ==20414== in use at exit: 228,493,230 bytes in 231,374 blocks ==20414== total heap usage: 1,036,615 allocs, 805,241 frees, 940,625,639 bytes allocated ==20414== ==20414== LEAK SUMMARY: ==20414== definitely lost: 160 bytes in 1 blocks ==20414== indirectly lost: 0 bytes in 0 blocks ==20414== possibly lost: 17,190,000 bytes in 78,969 blocks ==20414== still reachable: 211,301,054 bytes in 152,383 blocks ==20414== suppressed: 0 bytes in 0 blocks ==20414== Rerun with --leak-check=full to see details of leaked memory ==20414== ==20414== For lists of detected and suppressed errors, rerun with: -s ==20414== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Speicherzugriffsfehler (Speicherabzug geschrieben)``` finally …