Search Issue Tracker

Active

Under Consideration for 6000.0.X, 6000.2.X

Votes

0

Found in

6000.0.60f1

6000.2.6f1

Issue ID

UUM-125061

Regression

No

Crash with multiple stack traces when leaving a docked VFX Graph open

-

How to reproduce:
1. Open the attached “IN-120762” project
2. Open the “SmokeStack_Dark” VFX Graph
3. Wait for ~10 to 15 minutes
4. Observe the crash

Reproducible with: 6000.0.60f1, 6000.2.6f2
Could not test with: 6000.0.44f1 (could not open the “SmokeStack_Dark” VFX Graph), 6000.2.10f1, 6000.3.0b8, 6000.4.0a3 (reproduction is inconsistent- see notes)

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

Notes:
- The reporter mentions the crash is also reproducible when opening the “Skirt_Shad” Shader Graph in step 2
- Reproduction can be inconsistent ad/or take different amounts of time for the crash to occur
- The issue does not occur when the VFX Graph is undocked

First few lines of the stack trace:
0x00007FFA81D956B2 (Unity) D3D12PageAllocatorBase::RequestPage
0x00007FFA81DA7BFA (Unity) D3D12Page::Alloc
0x00007FFA81D70927 (Unity) D3D12CommandList::ReserveScratchMemory
0x00007FFA81D714CA (Unity) ConstantBuffersD3D12::ResetState
0x00007FFA81D9BC96 (Unity) D3D12ImmediateContext::BindShaders

or:
0x00007FFCED6A42A2 (Unity) D3D12PageAllocatorBase::RequestPage
0x00007FFCED6B7F28 (Unity) D3D12Page::Alloc
0x00007FFCED67F10F (Unity) D3D12CommandList::ReserveScratchMemory
0x00007FFCED6875CF (Unity) BufferD3D12::UpdateInternal
0x00007FFCED6858D6 (Unity) BufferD3D12::Update

or:
0x00007FFAFBD44C81 (nvwgf2umx) OpenAdapter10
0x00007FFAFBD36E2B (nvwgf2umx) OpenAdapter10
0x00007FFAFBD3A166 (nvwgf2umx) OpenAdapter10
0x00007FFAFBCBF98A (nvwgf2umx) OpenAdapter10
0x00007FFABA5FEFAF (D3D12Core) D3D12GetInterface

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.