Search Issue Tracker
Duplicate
Votes
1
Found in
2020.3
2021.1
2021.1.16f1
2021.2
2022.1
Issue ID
1354980
Regression
No
Editor crashes on SerializedFile::ReadObject when opening the project
Reproduction steps:
1. Open the attached project from the google drive link
2. Go to Assets > Reimport All
Reproducible with: 2020.3.16f1, 2021.1.16f1, 2021.2.0b6, 2022.1.0a2
Not reproducible with: 2022.1.0a3
Could not test with: 2019.4.29f1 (Due to various errors while downgrading)
First lines of the stacktrace:
0x00007ff61f89eed4 (Unity) SerializedFile::ReadObject
0x00007ff61f8834d1 (Unity) PersistentManager::ReadAndActivateObjectThreaded
0x00007ff61f881615 (Unity) PersistentManager::LoadObjectsThreaded
0x00007ff61f881354 (Unity) PersistentManager::LoadObjects
0x00007ff6201bd448 (Unity) ReloadNativeSourceAssets
Notes:
- The 2nd step is only needed when the project doesn't crash when opening
- Seems that "RockNew.physicMaterial.meta" and "RockNew.physicMaterial" might be the reason why the project crashes.
- Adding these two files to a new project doesn't produce the issue
- There were different stacktraces from testing on different versions
- Was not able to reproduce the issue from 2022.1.0a3 and higher, but it might be related to corrupted files
Comments (1)
-
fsedarkalex
Aug 05, 2021 16:05
I am the reporter of this issue.
The crash must somehow be tied to the GUID because I tried to recreate the physics material and manually patched the GUID in the .meta file -> got the same issue again with this new file.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
This is a duplicate of issue #1338910