System Information
Running: Windows 10 x64 with a gtx 1080 and plenty of ram.

Blender Version
2.78a

Alembic mesh created from "Quill" for Oculus frequently crashes in Blender. I'm not sure if Quill is creating bad geometry, or if Blender is behaving poorly, but I suspect Blender is at fault.

- has .abc file imported and relevant mesh isolated.
- source .abc file

Exact steps for others to reproduce the error
Here is some of the bad behavior I'm seeing:
-> Open the blend file.
-> Run the "separate" op.
-> Choose "Loose Parts"
-> Crashes with Error: EXCEPTION_ACCESS_VIOLATION
Not all mesh from Quill exhibit this crash, but the one attached does.

-> Open the blend file.
-> Run "degenerate dissolve" op.
-> Crashes with Error: EXCEPTION_ACCESS_VIOLATION
All Quill meshes that I've tested crash Blender doing this.

I think the issue lies with Blender. Maya doesn't seem to have any issue with this abc. If I exporting the mesh again from Maya -> Blender, Blender no longer crashes. It is possible that Maya fixes a problem with the mesh, or there is something unexpected in the way Quill is creating the Alembic file.

While the mesh does appear to have degenerate geometry (uv unwrapping it creates some very odd results), I'm not sure if this is a result of the import process or if it's in the actual abc file.