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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Nothing happens when entering a converter ID to target property in the Add Binding window when a converter ID was already added and removed
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
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.