It seems that this was 'fine', as non-trivial data in `BVHTreeFromMesh` appear to be 'safe' when simply zero-initialized instead of being properly constructed. Note that this 'calloced' data was already 'MEM_deleted', this is currently considered as a valid use-case unfortunately, otherwise the issue would have been detected earlier. Directly use 'copy' `MEM_new` code instead. Pull Request: https://projects.blender.org/blender/blender/pulls/135862