Before crashing a couple animation frames were rendered - in some frames, GetInput(kOfxMeshMainOutput).GetMesh() returned NULL mesh, which failed the cooking, while other frames cooked OK. This is the partially rendered animation (MfxVTK "Poke" effect):
When I tried to reproduce it, I got crash elsewhere. I'll report back if I learn more or make a reproducible test case.
I've encountered some strange behavior specifically when rendering animation (as opposed to rendering still frames or working in the viewport).
With https://github.com/eliemichel/OpenMeshEffectForBlender/commit/5b8b30afc8fdc9407d6fe49ede0ab3eca8938ec1 plus https://github.com/tkarabela/MfxVTK/commit/afdb181ea794c7a00b469c6ec89253c60f561394 (both debug builds, on Linux), I've tripped
stack-buffer-overflow
error in AddressSanitizer, regarding the stack-allocatedMeshInternalData
for output mesh.Before crashing a couple animation frames were rendered - in some frames,
GetInput(kOfxMeshMainOutput).GetMesh()
returned NULL mesh, which failed the cooking, while other frames cooked OK. This is the partially rendered animation (MfxVTK "Poke" effect):When I tried to reproduce it, I got crash elsewhere. I'll report back if I learn more or make a reproducible test case.