Search Issue Tracker
Active
Under Consideration for 6000.1.X
Votes
3
Found in
6000.1.3f1
Issue ID
UUM-107470
Regression
No
Crash on GfxDeviceD3D12::ProcessReleaseQueue when performing various Unity operations
A recurring crash issue in the Unity Editor has been observed, affecting various workflows. These crashes have been reported to happen when:
1. Opening a Unity project
2. Entering Play Mode
3. Working on Prefabs
4. Editing tile maps
Reproducible with versions: 6000.1.0f1, 6000.1.1f, 6000.1.2f1, 6000.1.3f1
Reproducible on: Windows 11 (reporter), Windows 10 (other reporters)
Note: Not reproduced by CQA
First few lines of the stack trace:
{noformat}0x00007FF9F0825156 (Unity) GfxDeviceD3D12::ProcessReleaseQueue
0x00007FF9F081AEB6 (Unity) GfxDeviceD3D12::EndOfFrameBookkeeping
0x00007FF9F0825A9C (Unity) GfxDeviceD3D12::QueuePresent
0x00007FF9F081B925 (Unity) D3D12Window::EndRendering
0x00007FF9F1FB0CAD (Unity) GfxDeviceWorker::RunCommand{noformat}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
- Files in the target folder are deleted without a proper warning when building an iOS project
Add comment