I'm unsure how to interpret a result from the 'Leak Checks' Instrument in 'Pure C' code. At the very beginning of a test run I see a leak reported. If I let the run proceed the test end occurs and the reported leak shows up with an 'Event Type' of 'free' - with a backtrace showing the exact function call sequence where I'd expect the memory to be freed.
Why am I getting a leak reported in the first place?
If this is a common 'false positive' then the only option I see is to check each reported leak to see if it actually got freed later. Let's just say 'tedious'.
Image shows a single leak, in the selected region. Looking at the history for that memory location shows a 'malloc' and a 'free' - why the leak?