There doesn't seem to be any way to avoid calling it or freeing (multiple) memory blocks allocated by it.
We're not interested in these (one off) leaks and can't do anything about them anyhow, so just provide a way too suppress leak sanitizer errors about them.