> Problem solved. You forgot "bypass or instrument our custom allocators", "determine repro steps in the first place", "filter out false positives", "bypass or

> Problem solved. You forgot "bypass or instrument our custom allocators", "determine repro steps in the first place", "filter out false positives", "bypass or instrument your refcounting - because failing to pair a free() with your malloc() isn't the problem, nor even failing to pair decRef()s with addRef()s - breaking up cycles is", etc. Sometimes the answer is "force your scripting language to garbage collect again". Sometimes the answer is "track down an incorrect cast in code that ultimately causes a single byte corruption in your refcount". Sometimes the answer is far more horrifying.