Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.12f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
7000.0.0a1
Issue ID
UUM-76813
Regression
No
[WinArm] Random crashes on GfxDeviceD3D12Base::DrawBuffersCommon when using the Editor
How to reproduce:
1. Create a new 3D URP project
2. Resize some Editor windows or leave the Editor idle
3. Observe the crash
Reproducible with: 6000.0.12f1
Not reproducible with: 2021.3.40f1, 2022.3.39f1
Reproducible on: Windows 11 (ARM)
Not reproducible on: No other environment tested
Notes:
-Crashes are unexpected but quite often
-It is not clear how to cause crashes consistently
Stacktrace:
0x00007FFF357AB330 (Unity) GfxDeviceD3D12Base::DrawBuffersCommon
0x00007FFF357AAD74 (Unity) GfxDeviceD3D12Base::DrawBufferRanges
0x00007FFF357AB00C (Unity) GfxDeviceD3D12Base::DrawBuffers
0x00007FFF36E18708 (Unity) GfxDeviceWorker::RunCommand
0x00007FFF36E1B274 (Unity) GfxDeviceWorker::RunExt
0x00007FFF36E1B3AC (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FFF354233E4 (Unity) Thread::RunThreadWrapper
0x00007FFFE6672310 (KERNEL32) BaseThreadInitThunk
0x00007FFFE6B35B2C (ntdll) RtlUserThreadStart
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.