.mdd & .pc2 export leave unfreed mesh data in memory killing Blender on larger animations #51627

New Issue

Kai Kostack · 2017-05-25T19:38:44+02:00

Kai Kostack commented

2017-05-25 19:38:44 +02:00

For a project I needed to export a larger mesh animation either as .mdd or .pc2 file. I was unable to do so because the exporters ran out of memory. The reason is that they are creating a new mesh data block per each frame but not deleting them after the data has been written to file which leads to a steadily increasing memory consumption the longer the animation sequence gets.

Here is one example, try to export it in either format and monitor memory usage:
1_export.blend

The solution is a one-liner deleting the data block afterwards by bpy.data.meshes.remove().

Try above test again with this patch and note the difference: patch.diff

System: Windows 7 x64

For a project I needed to export a larger mesh animation either as .mdd or .pc2 file. I was unable to do so because the exporters ran out of memory. The reason is that they are creating a new mesh data block per each frame but not deleting them after the data has been written to file which leads to a steadily increasing memory consumption the longer the animation sequence gets. Here is one example, try to export it in either format and monitor memory usage: [1_export.blend](https://archive.blender.org/developer/F609166/1_export.blend) The solution is a one-liner deleting the data block afterwards by bpy.data.meshes.remove(). Try above test again with this patch and note the difference: [patch.diff](https://archive.blender.org/developer/F609167/patch.diff) System: Windows 7 x64

Kai Kostack commented

2017-05-25 19:38:44 +02:00

Changed status to: 'Open'