Search Issue Tracker
Won't Fix
Votes
2
Found in [Package]
1.6.5
Issue ID
BUR-1889
Regression
Yes
Crash on Shader compilation when opening the project
See Comments for Repro Steps and Project
-Reproduction steps:-
-1. Open the attached 'Project' project-
-2. Observe crash-
Reproducible with: 2020.2.7f1, 2020.3.34f1, 2021.3.2f1, 2022.1.0b16, 2022.2.0a13
Not reproducible with: 2019.4.38f1, 2022.2.6f1
Error from the log file:
No explicit failure code handling for error of type 22
Shader compiler process initialization failed: Protocol error - failed to read magic number
Shader compiler: failed to launch and initialize compiler executable, even after 10 retries
Shader compiler initialization error: Protocol error - failed to read magic number
Cancelling DisplayDialog because it was run from a thread that is not the main thread: Fatal Error! Shader compiler initialization error: Protocol error - failed to read magic number|
Public Issue Tracker
[https://issuetracker.unity3d.com/product/unity/issues/guid/1411933/]
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
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note:
There are no fixes planned for this Bug in Burst 1.6.x
The issue does not occur in Burst 1.7.x or 1.5.x. Please Migrate to one of these versions if you experience this issue.
Burst 1.6.x will be deprecated by Burst 1.7.x in the future.