Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
0
Found in
2021.2
2021.2.0b4
2022.1
Issue ID
1352326
Regression
No
Crash on LoadShaders when opening up this project
How to reproduce:
1. Open the attached project from "Project link:"
2. Observe the crash
Reproducible with: 2021.2.0b7, 2022.1.0a5
Couldn't test with: 2018.4.36f1, 2019.4.29f1, 2020.3.16f1, 2021.1.17f1 (nvidia package problems)
First lines of the stack trace:
0x00007ff6f7fef29c (Unity) LoadShaders
0x00007ff6f7feef02 (Unity) LoadAndRegisterAllKnownShaders
0x00007ff6f7cebc9f (Unity) Application::InitializeProject
0x00007ff6f812d6a8 (Unity) WinMain
0x00007ff6f9420d62 (Unity) __scrt_common_main_seh
0x00007ff950d77034 (KERNEL32) BaseThreadInitThunk
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
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a7
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0b12