Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.34f1
2023.2.7f1
2023.3.0b4
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
7000.0.0a1
Issue ID
UUM-61705
Regression
No
[WinArm][DX11] Crash with Failed to present D3D11 swapchain
Steps to reproduce:
- Open any Unity project on a Windows Arm machine
- Open either File>Build Profiles... (Editor version 2023.3.0b3 and above) or Edit>Project Settings (other versions)
- Move or resize the window (the crash might reproduce as soon as the window starts rendering too)
Expected result: No crash
Actual result: The Editor crashes with the following error
Failed to present D3D11 swapchain due to device reset/removed.This error can happen if you draw or dispatch very expensive workloads to the GPU, which can cause Windows to detect a GPU Timeout and reset the device. (see https://docs.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery).If you believe this error is due to built-in Unity functionality, please submit a bug.This is an unrecoverable error and the editor will shut down.
Reproducible with: 2021.3.34f1, 2023.2.7f21, 2023.3.0b4, 6000.0.b12
Not reproducible with: 2022.3.18f1
Note:
- DX12 does not crash in a similar manner
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
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.