Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2022.1.X
Votes
0
Found in
2021.2.0a18
2021.2.14f1
2022.1
2022.2
Issue ID
1410540
Regression
Yes
Shader Compiler crashes when calling ComputeShader.GetKernelThreadGroupSizes with -nographics flag in Batch Mode
How to reproduce:
1. Open the attached project "bug-compute-shader-nographics.zip" to generate the "Library" folder and then close the Editor
2. Launch the Editor in Batch mode with the -nographics flag from Terminal (e.g. "/Applications/Unity/2021.2.14f1_bcb93e5482d2/Unity.app/Contents/MacOS/Unity -projectPath=/Applications/Unity/untitled folder/bug-compute-shader-nographics -batchmode -executeMethod Test.Run -quit -logFile Editor.log -nographics")
3. Observe the generated "Editor.log" from where you ran the command in the Terminal
Reproducible with: 2021.2.0a18, 2021.2.19f1, 2022.1.0b14, 2022.2.0a9
Not reproducible with: 2019.4.37f1, 2020.3.32f1, 2021.2.0a17
First lines of stack trace:
#0 GetStacktrace(int)
#1 CrashHandler(int)
#2 _sigtramp
#3 ???
#4 CgBatchCompileComputeKernel(core::basic_string<char, core::StringStorageDefault<char> >&, core::basic_string<char, core::StringStorageDefault<char> > const&, core::basic_string<char, core::StringStorageDefault<char> > const&, dynamic_array<core::pair<core::basic_string<char, core::StringStorageDefault<char> >, core::basic_string<char, core::StringStorageDefault<char> >, true>, 0ul> const&, dynamic_array<core::basic_string<char, core::StringStorageDefault<char> >, 0ul> const&, dynamic_array<core::basic_string<char, core::StringStorageDefault<char> >, 0ul> const&, BuildTargetPlatform, bool, bool, bool, std::__1::vector<unsigned char, std::__1::allocator<unsigned char> >&, ShaderCompilerPlatform, ShaderCompilationFlags, ShaderRequirements, unsigned int, unsigned int, void (*)(void*, CgBatchErrorType, int, int, char const*, char const*), void*)
#5 DispatchCommand(ShaderCompilerConnection&, core::basic_string<char, core::StringStorageDefault<char> > const&)
Notes:
1. The Editor crashes with a pop-up on 2021.2.14f1 only, a segmentation fault is printed in Terminal on other versions
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a12
Resolution Note (fix version 2022.1):
Fixed in 2022.1.3f1