21-08-2018, 01:17 AM
(20-08-2018, 04:11 AM)Jaydena Wrote: Thank you! this solution works a treat, but unfortunately it still creates a memory leak :/
I'm assuming in the UpdateMeshData function, a reference is created that doesn't allow the GC to remove the previous obicollider information.
Is there a way to call this action without slowly increasing the memory usage?
Thank you!
I solved the memory growth problem by commenting out the following 2 lines in ObiMeshShapeTracker.cs:
Line 83. meshDataCache[mesh] = handles;
Line 87. newHandles.Ref();
While i'm sure this creates some internal conflicts for Obi, all the fluid dynamics and mesh tracking seems to be working normally and without any problems.
Let me know if there's a safer way, but for now this solves the problem
Cheers!