Search Issue Tracker
Fixed
Fixed in 6000.2.7f1, 6000.3.0b4, 6000.4.0a2
Votes
5
Found in
6000.1.4f1
6000.2.3f1
Issue ID
UUM-107766
Regression
No
Crash on GfxDeviceD3D12Base::InitializeAsWorker when performing various Unity operations
A recurring crash issue has been observed when working in the Editor for some time.
Reproducible with versions: 6000.1.0f1 - 6000.1.4f1, 6000.2.3f1
Reproducible on: Windows 11 (reporter), Windows 10 (other reporters)
Notes:
- Not reproduced by CQA
- Reports from users with Intel and NVIDIA GPUs
First few lines of the stack trace:
{noformat}
0x00007FFCDA5523BA (Unity) GfxDeviceD3D12Base::InitializeAsWorker
0x00007FFCDA54CDAF (Unity) GfxDeviceD3D12::ExecuteCommandBuffersAsync
0x00007FFCDBCE0AE4 (Unity) GfxDeviceWorker::RunCommand
0x00007FFCDBCE391C (Unity) GfxDeviceWorker::RunExt
0x00007FFCDBCE3A4F (Unity) GfxDeviceWorker::RunGfxDeviceWorker{noformat}
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 6000.4.0a2):
Thank you for reporting a bug to Unity.
Newly implemented device filtering feature should fix this issue. Please re-report if your specific case still reproduces.
Resolution Note (fix version 6000.3.0b4):
Thank you for reporting a bug to Unity.
Newly implemented device filtering feature should fix this issue. Please re-report if your specific case still reproduces.
Resolution Note (fix version 6000.2.7f1):
Thank you for reporting a bug to Unity.
Newly implemented device filtering feature should fix this issue. Please re-report if your specific case still reproduces.