Search Issue Tracker
Won't Fix
Won't Fix in 6000.4.X
Votes
0
Found in
6000.0.60f1
6000.2.10f1
6000.3.0b7
6000.4.0a3
Issue ID
UUM-128984
Regression
No
[DX12] Crash on with multiple stack traces when rendering large Terrain with specific hardware
How to reproduce:
1. Open the attached “IN-122137.zip” project
2. Observe the crash
Reproducible in: 2023.2.0a1, 6000.0.60f1, 6000.2.10f1, 6000.3.0b7, 6000.4.0a3
Reproducible on: Windows 10 (RTX 2070 Super), Windows 11 (Intel(R) UHD Graphics)
Not reproducible on: Windows 11 (RTX 3080 Ti Laptop)
Notes:
- Could not reproduce in DirectX 11
- Reproduces with DirectX 12 and Vulkan
First few lines of stack trace (6000.3.0b7, DirectX 12):
0x00007FFFACD066BF (Unity) D3D12SwapChain::CreateHWND
0x00007FFFACCA5FCD (Unity) D3D12Window::D3D12Window
0x00007FFFACCE94AE (Unity) GfxDeviceD3D12Base::CreateGfxWindow
0x00007FFFACBBA934 (Unity) GfxDeviceWorker::RunCommand
Repro on DX12 call stack from
6000.0.23f1 (user repro):
{noformat}
========== OUTPUTTING STACK TRACE ==================
0x00007FFFF5153C35 (Unity) D3D12DescriptorHeapManager::AllocateNewResourceInternal
0x00007FFFF5136152 (Unity) D3D12PageAllocatorBase::AddNewResourceToThePool
0x00007FFFF5141FA3 (Unity) D3D12PageAllocatorBase::RequestPage
0x00007FFFF5115527 (Unity) D3D12ComputeCapableCommandList::GetDescriptorPage
0x00007FFFF5137617 (Unity) D3D12DeviceState::ApplyRenderTargets
0x00007FFFF5145487 (Unity) D3D12DeviceState::Transition
0x00007FFFF5105A4C (Unity) D3D12CommandListWithState::ApplyStateDrawcall
0x00007FFFF510F43A (Unity) GfxDeviceD3D12Base::DrawBuffersCommon
0x00007FFFF510EF9C (Unity) GfxDeviceD3D12Base::DrawBufferRanges
0x00007FFFF510F279 (Unity) GfxDeviceD3D12Base::DrawBuffers
0x00007FFFF4A9C875 (Unity) DynamicVBO::DrawChunk
0x00007FFFF68D90C1 (Unity) GfxDeviceWorker::RunCommand
0x00007FFFF68DBDEC (Unity) GfxDeviceWorker::RunExt
0x00007FFFF68DBF1D (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FFFF4D40A0D (Unity) Thread::RunThreadWrapper
0x00007FF91CD6E8D7 (KERNEL32) BaseThreadInitThunk
0x00007FF91E54C53C (ntdll) RtlUserThreadStart
========== END OF STACKTRACE ==========={noformat}
Stacktrace on 6000.3.0b7, 6000.4.0a3 (DX12):
{noformat}
========== OUTPUTTING STACK TRACE ==================
0x00007FFFACD066BF (Unity) D3D12SwapChain::CreateHWND
0x00007FFFACCA5FCD (Unity) D3D12Window::D3D12Window
0x00007FFFACCE94AE (Unity) GfxDeviceD3D12Base::CreateGfxWindow
0x00007FFFACBBA934 (Unity) GfxDeviceWorker::RunCommand
0x00007FFFACBBD4FC (Unity) GfxDeviceWorker::RunExt
0x00007FFFACBBD62F (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FFFAE467620 (Unity) Thread::RunThreadWrapper
0x00007FFFF70D7374 (KERNEL32) BaseThreadInitThunk
0x00007FFFF819CC91 (ntdll) RtlUserThreadStart
========== END OF STACKTRACE ==========={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
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
- FrameTimingManager.GetLatestTimings adds background time to the next focused frame when the Player is unfocused
- PropertyDrawer gets disposed while still being active when adding a secondary component
Resolution Note:
Need testing before create separate ticket
Resolution Note (6000.4.X):
Need testing before create separate ticket