Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.8f1
2023.1.10f1
2023.2.0b7
2023.3.0a3
Issue ID
UUM-47115
Regression
No
Crash after entering Play Mode when Rendering Path is set to "Forward+" and mouse cursor moves arbitrarily in Scene View
Reproduction steps:
1. Open the attached “repro-project“
2. Open the “Assets/Scenes/SampleScene.unity“ scene
3. In the Project window select the “Assets/New Universal Render Pipeline Asset_Renderer.asset” Asset
4. In the Inspector window make sure the Rendering Path is set to “Forward+“
5. Enter Play Mode
6. Open the Scene View
7. Move the mouse cursor arbitrarily
8. Observe the crash
Reproducible with: 2022.3.8f1, 2023.1.10f1, 2023.2.0b7, 2023.3.0a3
Fixed in: 2023.1.11f1 (for DirectX11 only)
Could not test with: 2021.3.30f1 (no “Forward+“ Rendering Path option)
Reproduced on: Windows 10 Pro, Windows 11 (by reporter)
Not reproducible on: No other environment tested
Notes:
1. Also reproduced in Player
2. Not reproducible when Rendering Path is set to “Forward“ or “Deferred“
3. Reproducible with DirectX11 and DirectX12
4. When using DirectX11 A pop-up appears when the crash occurs with the following information:
”Failed to present D3D11 swapchain due to device reset/removed. This error can happen if you draw or dispatch very expensive workloads to the GPU, which can cause
Windows to detect a GPU Timeout and reset the device. (see [https://learn.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery|https://learn.microsoft.com/en-us/windows-hardware/drivers/display/timeout-detection-and-recovery|smart-link]). If you believe this error is due to built-in Unity functionality, please submit a bug. This is an unrecoverable error and the editor will shut down.”
5. When using DirectX12 the Editor crashes with the following stack traces:
0x00007FF7E2A0CE6E (Unity) BufferD3D12::BeginWrite
0x00007FF7E279EA7F (Unity) GfxDevice::UpdateBufferRanges
0x00007FF7E40948ED (Unity) GfxDeviceWorker::RunCommand
0x00007FF7E4097DDB (Unity) GfxDeviceWorker::RunExt
0x00007FF7E4097EF8 (Unity) GfxDeviceWorker::RunGfxDeviceWorker0
0x00007FFE45C0DBCB (Unity) GfxDeviceD3D12Base::DrawBuffersCommon
0x00007FFE45C0CF4E (Unity) GfxDeviceD3D12Base::DrawBufferRanges
0x00007FFE45C0D1D0 (Unity) GfxDeviceD3D12Base::DrawBuffers
0x00007FFE4725E7E4 (Unity) GfxDeviceWorker::RunCommand
0x00007FFE4726155B (Unity) GfxDeviceWorker::RunExt
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
- Incorrect Shader keyword activation for Shadows when no Light is present in URP
- Editor freezes when loading a specific AssetBundle
- WebGPU builds with Multithreading enabled crash on Safari
- Set as Value in UI Builder doesn't work across all properties.
- Calculating time durations in RenderDoc with DX12 causes 'Device Lost error' popup
Resolution Note:
The cube in the binary asset bundle is using an old version of urp/lit shader. (probably before 2022.3.8f1). Recent version of unity doesn't provide comptible data to this old shader. Then, it enters infinite loop in forward+ and crash the GPU (timeout).
Unity doesn't support loading asset bundles built with older Unity