Search Issue Tracker
Won't Fix
Votes
6
Found in
6000.1.3f1
6000.2.0b13
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.0.47f1, 6000.1.0f1, 6000.1.1f, 6000.1.2f1, 6000.1.3f1
Reproducible on: Windows 11 (reporter), Windows 10 (other reporters)
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}
Comments (1)
-
Rob-Fireproof
Jul 14, 2025 10:25
I get a crash with the same callstack on 6000.1.10f1. I have a script which duplicates our world geometry multiple times (for the purposes of testing performance at scale), and then switch to the scene view and zoom out.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
This issue has been fixed in the following versions or later:
6000.0.58f1
6000.2.5f1
Thank you for reporting this issue.