Search Issue Tracker
Fixed in 2.2.0-exp.2
Votes
0
Found in [Package]
1.0.6, preview.1 - 2.0.0
Issue ID
1207084
Regression
Yes
Crash in aeDeleteObject or aeApplyMatrixV when importing an alembic(.abc) asset into the project
How to reproduce:
1. Download the user-attached alembic file(Alembic1.abc)
2. Create a new Unity project
3. Download the Alembic package
4. Drag Alembic1.abc into the Project window to import it
Expected result: the Editor does not crash
Actual result: the Editor crashes
Reproducible with: 2018.4.15f1, 2019.2.17f1, 2019.3.0f4, 2020.1.0a18
Could not test with: 2017.4.35f1(Alembic package unavailable)
Reproducible with package versions: 1.0.6, preview.1 - 2.0.0
Not reproducible with package versions: 1.0.5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Prefab Overrides “Apply” button is too big and overlaps with the context menu’s outline
- Prefab Overrides “No Overrides” text is too large, and the the Context Menu of the Parent GameObject has a lot of empty space when opened
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
Add comment