Search Issue Tracker

Fixed

Fixed in 6000.2.7f1, 6000.3.0b4, 6000.4.0a2

Votes

5

Found in

6000.1.4f1

6000.2.3f1

Issue ID

UUM-107766

Regression

No

Crash on GfxDeviceD3D12Base::InitializeAsWorker when performing various Unity operations

-

A recurring crash issue has been observed when working in the Editor for some time.

Reproducible with versions: 6000.1.0f1 - 6000.1.4f1, 6000.2.3f1

Reproducible on: Windows 11 (reporter), Windows 10 (other reporters)

Notes:
- Not reproduced by CQA
- Reports from users with Intel and NVIDIA GPUs

First few lines of the stack trace:
{noformat}
0x00007FFCDA5523BA (Unity) GfxDeviceD3D12Base::InitializeAsWorker
0x00007FFCDA54CDAF (Unity) GfxDeviceD3D12::ExecuteCommandBuffersAsync
0x00007FFCDBCE0AE4 (Unity) GfxDeviceWorker::RunCommand
0x00007FFCDBCE391C (Unity) GfxDeviceWorker::RunExt
0x00007FFCDBCE3A4F (Unity) GfxDeviceWorker::RunGfxDeviceWorker{noformat}

  1. Resolution Note (fix version 6000.4.0a2):

    Thank you for reporting a bug to Unity.

    Newly implemented device filtering feature should fix this issue. Please re-report if your specific case still reproduces.

  2. Resolution Note (fix version 6000.3.0b4):

    Thank you for reporting a bug to Unity.

    Newly implemented device filtering feature should fix this issue. Please re-report if your specific case still reproduces.

  3. Resolution Note (fix version 6000.2.7f1):

    Thank you for reporting a bug to Unity.

    Newly implemented device filtering feature should fix this issue. Please re-report if your specific case still reproduces.

Add comment

Log in to post comment