Search Issue Tracker
Fixed in 2022.2.X
Votes
2
Found in
2021.2.0a1
2021.2.4f1c1
2022.1
Issue ID
1384314
Regression
Yes
Crash when importing a specific FBX asset
How to reproduce:
1. Open a new Unity project
2. Try to import the "crash_fbx.FBX" asset
Expected result: The FBX asset imports successfully
Actual result: Editor crashes when trying to import the FBX asset
Reproducible with: 2021.2.0a1, 2021.2.5f1, 2022.1.0b1
Not reproducible with: 2019.4.33f1, 2020.3.24f1, 2021.1.0a10, 2021.1.28f1
Notes:
- Bug reporter message: "Start importing Assets/1384314_crash_fbx.FBX using Guid(1a60dfb9eff004f1cafd0a1c5024b02e) Importer(-1,00000000000000000000000000000000) Obtained 0 stack frames."
Comments (2)
-
NicolasSouza-NIckSDev
Oct 17, 2022 16:07
"Fixed on 2022" it´s not consider a Fix because you jump over 2021 LTS (as usually does)
-
cryogee
Feb 22, 2022 19:31
Workaround I used: FBX import was working with earlier version 2021.1.X , So I imported the FBX using those. Then I Used Unity FBX Exporter. This you can add to your project using Packages. The FBX exported from FBX exporter were imported successfully into the original project without any errors.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
- Visual Studio Code does not integrate with the project when the .slnx project is opened
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a10