Search Issue Tracker
Active
Under Consideration for 6000.4.X
Votes
0
Found in
6000.0.60f1
6000.2.10f1
6000.3.0b7
6000.4.0a3
Issue ID
UUM-125265
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment