Search Issue Tracker
Won't Fix
Votes
1
Found in
2022.3.14f1
Issue ID
UUM-57539
Regression
No
Crash on D3D12GetInterface when entering the Play mode
Reproduction steps:
1. Open the attached project "CrashRepro"
2. Enter the Play Mode
3. If it does not crash close and reopen the project and repeat step 2
Expected result: The Play mode starts
Actual result: Editor crashes
Reproducible with: 2022.2.0b1, 2022.3.14f1
Not reproducible with: 2023.1.0a1, 2023.2.1f1, 2023.3.0a16
Couldn’t test with: 2021.3.32f1 - “ArgumentException: RenderTextureDesc width must be greater than zero. Parameter name: desc.width“, 2022.1.0a1-2022.2.0a18 crashes on ValidateLateShader when opening
Reproducible on: Windows 10
Not reproducible on: No other environment tested
First few lines of stack trace:
{noformat}
0x00007FF8F2EB9CF9 (D3D12Core) D3D12GetInterface
0x00007FF6CD835537 (Unity) FillTableUNIAndBarrier
0x00007FF6CD83220A (Unity) CmdListFillTableUNI
0x00007FF6CD830A9C (Unity) D3D12DeviceState::ApplyResources
0x00007FF6CD83CEDF (Unity) D3D12DeviceState::Transition
0x00007FF6CD830DA8 (Unity) D3D12CommandListWithState::ApplyStateDrawcall{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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.