Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
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}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
- WebGL Player does not proceed beyond logo screen when "Target WebAssembly 2023" is enabled
Add comment