==10675== Memcheck, a memory error detector
==10675== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al.
==10675== Using Valgrind-3.25.1 and LibVEX; rerun with -h for copyright info
==10675== Command: speed-dreams-2
==10675== Parent PID: 3961
==10675== 
==10675== Warning: --freelist-big-blocks value 1000000 has no effect
==10675== as it is >= to --freelist-vol value 0
==10675== Jump to the invalid address stated on the next line
==10675==    at 0x228BB7DC: ???
==10675==    by 0x228BB8D4: ???
==10675==    by 0x228E4BB2: ???
==10675==    by 0x228E6A93: ???
==10675==    by 0x228E6ED4: ???
==10675==    by 0x228EDCCA: ???
==10675==    by 0x4C162D0: __run_exit_handlers (exit.c:118)
==10675==    by 0x4C163AD: exit (exit.c:148)
==10675==    by 0x4BFD5FB: (below main) (libc_start_call_main.h:74)
==10675==  Address 0x228bb7dc is not stack'd, malloc'd or (recently) free'd
==10675== 
==10675== 
==10675== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==10675==  Access not within mapped region at address 0x228BB7DC
==10675==    at 0x228BB7DC: ???
==10675==    by 0x228BB8D4: ???
==10675==    by 0x228E4BB2: ???
==10675==    by 0x228E6A93: ???
==10675==    by 0x228E6ED4: ???
==10675==    by 0x228EDCCA: ???
==10675==    by 0x4C162D0: __run_exit_handlers (exit.c:118)
==10675==    by 0x4C163AD: exit (exit.c:148)
==10675==    by 0x4BFD5FB: (below main) (libc_start_call_main.h:74)
==10675==  If you believe this happened as a result of a stack
==10675==  overflow in your program's main thread (unlikely but
==10675==  possible), you can try to increase the size of the
==10675==  main thread stack using the --main-stacksize= flag.
==10675==  The main thread stack size used in this run was 8388608.
==10675== 
==10675== HEAP SUMMARY:
==10675==     in use at exit: 4,323,532 bytes in 51,568 blocks
==10675==   total heap usage: 3,717,966 allocs, 3,666,398 frees, 1,212,005,626 bytes allocated
==10675== 
==10675== LEAK SUMMARY:
==10675==    definitely lost: 116,312 bytes in 279 blocks
==10675==    indirectly lost: 457,188 bytes in 11,270 blocks
==10675==      possibly lost: 15,766 bytes in 42 blocks
==10675==    still reachable: 3,616,850 bytes in 38,933 blocks
==10675==         suppressed: 240 bytes in 1 blocks
==10675== Rerun with --leak-check=full to see details of leaked memory
==10675== 
==10675== For lists of detected and suppressed errors, rerun with: -s
==10675== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)