I was using the Visual Studio 2019 Diagnostic Tools' Memory Usage tool on Windows 10.
After a bit of digging and prodding I ended up with this test, where I call a function to import a gltf and return. This is from the main function.
There are two breakpoints, 1 before the importing function is called and 2 after the function is called. Snapshots of the heap allocated are taken and it shows the following. I am interpreting this as the cgltf_data that was allocated is not being freed correctly.
Main function
The which imports the gltf into a cgltf_data and frees the data.
The snapshot of the heap at the breakpoint at the return statement. Ideally there should be no values here.
This is the call stack snapshot.
Tried with imported 3 gltf files and the "count" parameter in the snapshot goes to 3.
Please let me know if you need more information, and if there is another way to verify this.
nihalkenkre
commented
4 years ago
Hello.
I was using the Visual Studio 2019 Diagnostic Tools' Memory Usage tool on Windows 10.
After a bit of digging and prodding I ended up with this test, where I call a function to import a gltf and return. This is from the main function.
There are two breakpoints, 1 before the importing function is called and 2 after the function is called. Snapshots of the heap allocated are taken and it shows the following. I am interpreting this as the cgltf_data that was allocated is not being freed correctly.
Main function
The which imports the gltf into a cgltf_data and frees the data.
The snapshot of the heap at the breakpoint at the return statement. Ideally there should be no values here.
This is the call stack snapshot.
Tried with imported 3 gltf files and the "count" parameter in the snapshot goes to 3.
Please let me know if you need more information, and if there is another way to verify this.
Best regards. Nihal Kenkre.