Search Issue Tracker
Active
Under Consideration for 6000.1.X
Votes
4
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}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Quest] Pitch Shifter causes audio degradation on Quest 2 devices when sped up
- "GUI Error: Invalid GUILayout" and "NullReferenceException" are thrown when adding Scenes to "Scenes in Baking Set" in Adaptive Probe Volumes
- Inspector window not updating when switching GameObjects in Play Mode while having a VR headset connected
- “UnityException: GetInvalidFilenameChars” errors are thrown, and the Overlay Save Preset button becomes unusable when entering Play Mode with a shortcut while Overlay Save Preset window is opened
- "UnityException: GetName can only be called from the main thread." erors are thrown when the Shortcuts window is opened and entering Play Mode with a shortcut
Add comment