Search Issue Tracker
Fixed
Fixed in 6000.3.14f1, 6000.4.4f1, 6000.5.0b5, 6000.6.0a4
Won't Fix in 6000.0.X
Votes
0
Found in
6000.0.72f1
6000.3.12f1
6000.4.1f1
6000.5.0b2
6000.6.0a2
Issue ID
UUM-138597
Regression
Yes
Crash on CheckDeviceStatus when selecting GameObjects in the scene view while using DX12
How to reproduce:
1. Open the attached “IN-138201“ project
2. Open the “SampleScene”
3. Click around in the scene view until the “InspectorWindow.Repaint” loading bar appears
4. Wait for a couple minutes
5. Observe the crash
Reproducible with: 6000.0.10f1, 6000.0.72f1, 6000.3.12f1, 6000.4.1f1, 6000.5.0b2, 6000.6.0a2
Not reproducible with: 6000.0.9f1
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
- Sometimes, it takes multiple tries for the crash to occur
- Not reproducible with DX11 or Vulkan
- Issue is quite inconsistent- FAV may not be accurate
First few lines of the stack trace:
0x00007FFD035B61E0 (Unity) CheckDeviceStatus
0x00007FFD03546795 (Unity) D3D12CommandList::PrepareExecute
0x00007FFD0355F130 (Unity) GfxTaskExecutorD3D12::DoExecute
0x00007FFD035654EF (Unity) GfxTaskExecutorD3D12::RunTask
0x00007FFD0356809E (Unity) GfxTaskExecutorD3D12::Task
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
- Changing Signing organization on a Template still shows the same organization in the Hub
- [Android] Navigation bar does not go away when tapping on the screen to close the keyboard
- "InvalidOperationException" is thrown when clicking "Ctrl+Z" after opening Gradient Editor
- Breadcrumbs don't change names when graphs are renamed
- Adaptive Probe Volumes require a second bake for correct probe lighting data when Min Probe Spacing is changed in URP
Resolution Note:
Fixed in 6000.6.0a4
Resolution Note (fix version 6000.6.0a4):
Fixed in 6000.6.0a4
Resolution Note (fix version 6000.5.0b5):
Fixed in 6000.5.0b5
Resolution Note (fix version 6000.4.4f1):
Fixed in 6000.4.4f1
Resolution Note (fix version 6000.3.14f1):
Fixed in 6000.3.14f1
Resolution Note (6000.0.X):
Thank you for reporting a bug to Unity.
This issue will be fixed in an upcoming release. We have reviewed the issue carefully, and in this case, the team is unable to prioritize backporting this bug to existing releases. 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 a backport may destabilize a release in production.
Today we will be closing this port. 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.