Search Issue Tracker
Duplicate
Duplicate in 2020.3.X
Votes
0
Found in
2020.2.0a11
2020.2.7f1
2020.3
Issue ID
1324965
Regression
Yes
Crash on FixupCg when opening a project with specific group of assets
How to reproduce:
1. Open the attached project from link labeled "crash1324965"
2. Observe crash
Reproducible with: 2020.2.0a11, 2020.3.4f1
Not reproducible with: 2018.4.34f1, 2019.4.24f1, 2020.2.0a10, 2021.1.3f1, 2021.2.0a13
First lines of stack trace:
0x00007ff7174c0783 (Unity) FixupCg
0x00007ff7174cc9c1 (Unity) UpgradeOldShaderSyntax
0x00007ff717468732 (Unity) UpgradeShader
0x00007ff717469679 (Unity) UpgradeShadersIfNeeded
0x00007ff71741fcac (Unity) Application::InitializeProject
Note:
1. Deleting "Library" or "Project Settings" or any temp folders in the project's directory doesn't fix the issue
2. Seems like a combination of assets is the culprit of the crash
-
Resolution Note (2020.3.X):
Fixed in 2020.3.5f1
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 #1299790