Search Issue Tracker

Fixed

Fixed in 6000.3.6f1, 6000.4.0b5, 6000.5.0a4

Votes

0

Found in

6000.2.7f1

6000.3.0a4

6000.4.0a1

6000.5.0a1

Issue ID

UUM-122030

Regression

Yes

Crash with multiple stack traces when opening a specific project for the first time

DirectX12

-

How to reproduce:
1. Open the attached “IN-114956” project
2. Observe the crash

Reproducible with: 6000.2.0b2 (d4c40f50eb81), 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Not reproducible with: 6000.0.59f1, 6000.2.0b1 (d17678da8412)

Reproduced on: Windows 10 (user reported), Windows 11
Not reproduced on: No other environment tested

Note: The project opens successfully on the second try

First few lines of the stack trace:
User stack trace:
0x00007FFA34D71472 (Unity) D3D12PageAllocatorBase::RequestPage
0x00007FFA34D84E1A (Unity) D3D12Page::Alloc
0x00007FFA34D4D59F (Unity) D3D12CommandList::ReserveScratchMemory
0x00007FFA34D4D513 (Unity) D3D12UploadOperation::Reserve
0x00007FFA34D8D484 (Unity) TexturesD3D12::UploadTextureDataInternal

Obtained stack trace:
0x00007FFB3FE2C355 (nvwgf2umx) NVAPI_Thunk
0x00007FFB3FE34D3D (nvwgf2umx) NVAPI_Thunk
0x00007FFB3FCBC603 (nvwgf2umx) NVAPI_Thunk
0x00007FFB3FDF0397 (nvwgf2umx) NVAPI_Thunk
0x00007FFB3FDEF00E (nvwgf2umx) NVAPI_Thunk

  1. Resolution Note:

    Fixed a crash that occurred due to kernel memory exhaustion when a texture was modified using Texture2D.Apply a high number of times within a single frame

  2. Resolution Note (fix version 6000.5.0a4):

    Fixed a crash that occurred due to kernel memory exhaustion when a texture was modified using Texture2D.Apply a high number of times within a single frame

  3. Resolution Note (fix version 6000.4.0b5):

    Fixed in 6000.4.0b5

  4. Resolution Note (fix version 6000.3.6f1):

    Fixed in 6000.3.6f1

Log in to vote on 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.

Latest issues

See all new issues