Search Issue Tracker
Won't Fix
Votes
1
Found in
6000.0.6f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
Issue ID
UUM-73971
Regression
No
[DX11-repro] Crash on GfxDeviceD3D12Base::DrawBuffersCommon when changing a specific prefab
Reproduction steps:
1. Open the attached project "CrashRepro"
2. Open “Hair“ prefab
3. In the “Explorer: Ready“ window switch the strategy from “Random“ to “FullTestPass“ until it crashes
Expected result: Strategy is changed
Actual result: Editor crashes
Reproducible with: 6000.0.6f1
Couldn’t test with: 2021.3.39f, 2022.3.31f1 - Packages errors and “Explorer: Ready“ window doesn't appear
Reproducible on: Windows 10
Not reproducible on: macOS Sonoma 14.5 (Intel)
Note: During step 3 the dropdown selection window sometimes appears in a random location
First few lines of the stack trace:
{noformat}0x00007FFA82D1915B (Unity) GfxDeviceD3D12Base::DrawBuffersCommon
0x00007FFA82D18C86 (Unity) GfxDeviceD3D12Base::DrawBufferRanges
0x00007FFA82D18F49 (Unity) GfxDeviceD3D12Base::DrawBuffers
0x00007FFA844D300A (Unity) GfxDeviceWorker::RunCommand
0x00007FFA844D63EC (Unity) GfxDeviceWorker::RunExt{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
- Query Builder items display raw code style names instead of human readable labels in search field
- “+” button does nothing and has no functionality when clicked in Human Template "Bone Template" list
- Solid gray or black areas are present when using ShaderGraph with Custom Function nodes without manual reimport
- The Multiplayer Play mode tool doesn't see the list of Play Mode scenarios when using 6000.3.x
- Input field does not update when selecting the same input field after previous input was canceled
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.