As a current workaround, as I just found out, you can apparently just nil the dispatcher yourself before the threads join:
`getGlobalDispatcher(nil)` That gets rid of all leaks related to the dispatcher that I had so far.
- Understanding an address sanitizer message for a memory leak caus... Isofruit
- Understanding an address sanitizer message for a memory leak... Isofruit
- Understanding an address sanitizer message for a memory ... mratsim
- Understanding an address sanitizer message for a mem... Isofruit
- Understanding an address sanitizer message for a... Isofruit
