When building TracyClient.cpp and calling _CrtDumpMemoryLeaks() i'm seeing a leak of 16416 bytes. Looks like a global constructor is allocating memory. I'm sure it gets cleaned up but it would be nice to have control over this. Currently our code has to allow for this leak in its shutdown memory checks. Maybe explicit initialisation/shutdown calls?
When building TracyClient.cpp and calling _CrtDumpMemoryLeaks() i'm seeing a leak of 16416 bytes. Looks like a global constructor is allocating memory. I'm sure it gets cleaned up but it would be nice to have control over this. Currently our code has to allow for this leak in its shutdown memory checks. Maybe explicit initialisation/shutdown calls?