Search Issue Tracker
Won't Fix
Votes
2
Found in
2022.3.39f1
6000.0.10f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
Issue ID
UUM-76231
Regression
No
Crash on D3D12GetInterface when saving on a specific project
Reproduction steps:
1. Open the attached project "CrashRepro"
2. Select “Aset_rock_granite_M_rgAsy“ in the Hierarchy and move it in the scene
3. Save the scene
4. If it does not crash repeat from step 2
Expected result: Project is saved
Actual result: Editor crashes
Reproducible with: 2022.3.39f1, 6000.0.10f1
Couldn’t test with: 2021.3.40f1 (textures broken, package errors)
Reproducible on: Windows 10
Not reproducible on: No other environment tested
Note: It creates a memory leak when opening Game view with FSR enabled on the camera due to another bug
First few lines of stack trace:
{noformat}0x00007FFC5679DC74 (D3D12Core) D3D12GetInterface
0x00007FFC456D6870 (Unity) GfxDeviceD3D12Base::CopyTexture
0x00007FFC46E9655F (Unity) GfxDeviceWorker::RunCommand
0x00007FFC46E9FB6C (Unity) GfxDeviceWorker::RunExt
0x00007FFC46E9FC9D (Unity) GfxDeviceWorker::RunGfxDeviceWorker{noformat}
Comments (2)
-
GhostAspirine
Aug 19, 2024 00:43
Reproduced in 6.15f1
-
GhostAspirine
Jul 29, 2024 23:55
Reproduce in 6.12f1
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.