Page MenuHome

Alembic Crash (parenting to alembic)
Closed, ResolvedPublic


System Information
Win 7 64 Ult
GeForce GTX 580 1.5 GB

Blender Version
Broken: 50a44ed-win64
Worked: -

Short description of error
Alembic exported from 3ds Max 2016

If the exported alembic has an Empty (in 3ds Max called Point Helper), parent something to that helper, once you save a file and reOpen it - instant crash when you enable the layer where the Empty or the child object of that Empty is.

Note, you have to save the blend file and then reopen!

After more testing, it seems that just adding another object to a new layer will make Blender crash, after saving and reopen, when the layer where the Emptys are is enabled

Exact steps for others to reproduce the error

2 files are provided:


  • When you open alembic.blend, you are on Layer 2. and you can enable visibility on all layers without crashing.
  • Layer 1 has the imported Alembic Emptys.
  • Layer 2 has a cube created in Blender


  • In this file all I had done was add a Torus on Layer 11, and this was enough to create the crash.
  • When you open alembic_crash.blend, you are on Layer 11. and you can enable visibility on Layer 2 without a crash. If you enable Layer 1, it will crash Blender.
  • Layer 1 has the imported Alembic Emptys.
  • Layer 2 has a cube created in Blender
  • Layer 11 has a torus created in Blender


Let me know if you need more info.

Event Timeline

After further testing, I was able to narrow it done more specifically.
Even when you open the file that does not crash:

Just "Save As", and once you reopen that file, enable Layer 1 (where alembic empties are) and Blender will crash.

It seems that the saving and reopening is something that triggers it.

Crash was caused by an invalid cache file pointer in the transform cache constraint added to the empties. The pointer is invalid because it can't locate the alembic archive on disk (which is missing from, not attached to, the report). Anyway, it should be fixed now, thanks for the report!