Discussion on unmanaged memory leak

[sr229]

Based on what @Speykious and I dug, we narrowed down our memory leak to our managed code not calling the unmanaged deleters, leaving us with dangling pointers that has not been cleared.

Related Literature

@dbruning findings and memory profile shared to us

Memory Footprints of MediaPipe natively by @Speykious

[Speykious]

While memory does leak, after a lot more digging into the MediaPipe code, we actually determined that the cause was not that deleters weren't called, but that we were using non-thread-safe MediaPipe classes in a multithreaded context.
We'll try to recreate an example once SeeShark 3.0 is release as it will expose synchronous functions.

[sr229]

While we solved this already on 5226aef, I wouldn't call it "case closed" as we don't have an assurance we can maintain that it won't leak anywhere. Hence we're closing this only once MUXR has been implemented.