Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.27f1
6000.1.0a5
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-87332
Regression
No
Crash on D3D12GetInterface when reopening a specific project (AMDUnityPlugin)
Reproduction steps:
1. Open the attached project "CrashRepro"
2. Close the project
3. Open the project
Expected result: Project opens
Actual result: Editor crashes
Reproducible with: 6000.0.27f1, 6000.1.0a5
Couldn’t test with: 2021.3.46f1, 2022.3.52f1 - scene broken
Reproducible on: Windows 11
Not reproducible on: No other environment tested
First few lines of stack trace:
{noformat}2024-10-31T12:55:09.717Z|0x6070|0x00007FFD4896B05A (D3D12Core) D3D12GetInterface
2024-10-31T12:55:09.717Z|0x6070|0x00007FFD4896ACCC (D3D12Core) D3D12GetInterface
2024-10-31T12:55:11.512Z|0x6070|0x00007FFD500EA717 (Unity) GfxTaskExecutorD3D12::DoExecuteFromPlugin
2024-10-31T12:55:11.594Z|0x6070|0x00007FFD5187C877 (Unity) ExecuteCommandListImpl
2024-10-31T12:55:11.598Z|0x6070|0x00007FFD49659D9C (AMDUnityPlugin) ffxFsr2GetRenderResolutionFromQualityMode
2024-10-31T12:55:11.598Z|0x6070|0x00007FFD49656513 (AMDUnityPlugin) ffxFsr2GetRenderResolutionFromQualityMode
2024-10-31T12:55:11.656Z|0x6070|0x00007FFD500F419D (Unity) GfxTaskExecutorD3D12::RunTask{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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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.