Search Issue Tracker

Won't Fix

Won't Fix in 6000.5.X

Votes

0

Found in

6000.0.60f1

6000.2.8f1

6000.3.0b5

6000.4.0a2

6000.5.0a1

Issue ID

UUM-122105

Regression

No

Crash with multiple stack traces when painting detail on Terrain with a highly detailed Prefab

Terrain

-

How to reproduce:
1. Open the attached “IN-115703” project
2. Open the “SampleScene”
3. In the Hierarchy, click on the “Terrain”
4. In the Inspector under the “Terrain” component, select “Paint Details”
5. Under the Details section, select “Edit Details” > “Add Detail Mesh”
6. Drag the “Grars2” Prefab into the “Detail Prefab“ slot
7. Click the “Add” button in the bottom right corner
8. In the Scene view, paint the detail onto the Terrain
9. Observe the crash

Reproducible with: 2023.1.0a1, 6000.0.60f1, 6000.2.8f1, 6000.3.0b5, 6000.4.0a2

Reproduced on: Windows 11
Not reproduced on: No other environment tested

Note: Sometimes, an infinite loading cycle occurs instead of a crash

First few lines of the stack trace:
6000.4.0a2
0x00007FFBCEB50832 (nvwgf2umx) OpenAdapter10
0x00007FFC84B4EAE5 (D3D12Core) D3D12GetInterface
0x00007FFBDC9DC36B (Unity) GfxDeviceD3D12::GpuRecorderResolveTimestamps
0x00007FFBDCC4E4F3 (Unity) GpuRecorderManager::FrameTick
0x00007FFBDC5A44A7 (Unity) GfxDeviceWorker::RunCommand

6000.3.0b5
0x00007FFBCEA482E2 (Unity) D3D12PageAllocatorBase::RequestPage
0x00007FFBCE9EB328 (Unity) D3D12Page::Alloc
0x00007FFBCE9F222D (Unity) D3D12CommandList::ReserveScratchMemory
0x00007FFBCEA0AB85 (Unity) FillRootConstantBuffers
0x00007FFBCEA07975 (Unity) CmdListFillTableUNI

6000.2.8f1
0x00007FFBCEB4F4B4 (nvwgf2umx) OpenAdapter10
0x00007FFBCEC4A867 (nvwgf2umx) OpenAdapter12
0x00007FFC94898505 (D3D12Core) D3D12GetInterface
0x00007FFBDB5F117A (Unity) D3D12DeviceState::ApplyRenderTargets
0x00007FFBDB5FC407 (Unity) D3D12DeviceState::Transition

  1. 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.

  2. Resolution Note (6000.5.X):

    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.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.