Search Issue Tracker
Won't Fix
Won't Fix in 6000.0.X
Votes
0
Found in
2022.1.8f1
2022.2.0a18
2023.1.0a1
2023.2.0a1
2023.3.0a3
6000.0.0b11
Issue ID
UUM-2876
Regression
No
[DX12] Editor crashes on GfxTaskExecutorD3D12::DoExecute or GeometryJobTasks::ScheduleGeometryJobs when using using batchmode
How to reproduce:
1. Download the project (Link in the Edit below)
2. Open the Unity Editor folder and execute the following command - Unity.exe -batchmode -runTests -assemblyNames “PlayModeTests” -projectPath "PROJECT_PATH" -testResults "PROJECT_PATH/results.xml" -testPlatform PlayMode -logfile
3. Inspect the Editor logs
Expected results: The command is executed and the tests are run
Actual results: Editor crashed with GfxTaskExecutorD3D12::DoExecute or GeometryJobTasks::ScheduleGeometryJobs
Reproducible with: 2022.1.0f1, 2022.2.0a11
Could not test with: 2019.4.38f1, 2020.3.33f1, 2021.3.1f1 (Downgrading the project requires significant changes for it to compile. After those modifications are done the crash no longer occurs when the project is upgraded back to the version where it previously has crashed)
Notes:
1. The crash does not occur if -force-d3d11 argument is used
2. The crash does not occur if -batchmode is not used
3. The crash does not occur if the Editor is run normally
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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (6000.0.X):
There are no fixes planned for this Bug