Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.1.0f3
Issue ID
947508
Regression
No
[Mac] Force Quitting Unity results in an Unhandled Exception in the Shader Compiler log
Reproduction steps:
1. Create a new project
2. Force Quit Unity
3. Open the "ShaderCompiler.log" inside of the Projects Library folder
Expected Result: The Shader Compiler process should end without any unhandled exceptions if Force Closed
Actual Result: "Unhandled exception: Protocol error - failed to read correct magic number" is thrown
Fixed in: 2018.1.0a3
Reproduced with: 2017.3.0b1, 2017.2.0f1, 2017.1.1p2, 5.6.3p3, 5.5.4p5
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
Add comment