Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.36f1
2022.3.25f1
Issue ID
UUM-70219
Regression
No
Crash on GfxDeviceD3D12Base::DrawBuffersCommon when opening a specific project
Reproduction steps:
1. Open the attached project "CrashRepro"
Expected result: Project opens
Actual result: Editor crashes
Reproducible with: 2021.3.36f1, 2022.3.25f1
Not reproducible with: 2023.1.0a1, 2023.2.16f1, 6000.0.0b15
Reproducible on: Windows 10
Not reproducible on: No other environment tested
First few lines of stack trace:
{noformat}0x00007FF7106334AB (Unity) GfxDeviceD3D12Base::DrawBuffersCommon
0x00007FF71063274E (Unity) GfxDeviceD3D12Base::DrawBufferRanges
0x00007FF7106329D0 (Unity) GfxDeviceD3D12Base::DrawBuffers
0x00007FF711C732D2 (Unity) GfxDeviceWorker::RunCommand
0x00007FF711C7605B (Unity) GfxDeviceWorker::RunExt
0x00007FF711C76178 (Unity) GfxDeviceWorker::RunGfxDeviceWorker{noformat}
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
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.