In #33, we fixed an excessive allocation issue (#32) by redefining the faces' geometry and storage (Face%geom and Face%storage) as pointers. This fixed the memory leak that was reported when loading very large meshes (e.g., CRM meshes). However, pointers might create other types of memory leak issues (for instance, see the fix horses-framework/horses3d#287). That's why, we would like to remove these pointers if possible.
At the time of opening this issue, the fix implemented in #33 doesn't have any reported memory leak problems.
In #33, we fixed an excessive allocation issue (#32) by redefining the faces' geometry and storage (
Face%geomandFace%storage) as pointers. This fixed the memory leak that was reported when loading very large meshes (e.g., CRM meshes). However, pointers might create other types of memory leak issues (for instance, see the fix horses-framework/horses3d#287). That's why, we would like to remove these pointers if possible.At the time of opening this issue, the fix implemented in #33 doesn't have any reported memory leak problems.