Search Issue Tracker

Active

Under Consideration for 6000.1.X

Votes

3

Found in

6000.1.0f1

6000.1.1f1

Issue ID

UUM-104855

Regression

No

[AMD] Crash on VerifyD3DTextureSharingCallback when creating a new project

-

Reproduction steps:
1. Create and open a new Universal 2D/3D project
2. Observe the crash

Reproducible with: 6000.1.0f1, 6000.1.1f1

Reproducible on: Windows 10 (22H2) (user's), Windows 11 (24H2) (user's)
Not reproducible on: No other environments tested

Notes:
* Not reproduced by CQA
* Launching with -force-vulkan command-line argument doesn't fix the crash
* All of the reports are with AMD Radeon GPUs and Windows
* Disabling the AMD Radeon GPU on the device fixes the issue
* Forcing the Editor to launch with OpenGL as the graphics API fixes the issue
* Only one report is with a non-HD-branded 6600M/6700M card (which was produced around 2021), and it was reported on Windows 11 (24H2)
* All other reports are with AMD Radeon HD cards (which were produced between 2007 and 2013; so far the reports are with 5450, 5700, 6550D, 6570, 6800, 7000, 7500M, 7600M, 7660D, 7660G, 8370D, 8570D, and 8670D) and they're all reported on Windows 10 (22H2)
* Appears to only happen on DirectX11

First few lines of the stack trace:
0x00007FFE50B3311F (Unity) VerifyD3DTextureSharingCallback
0x00007FFE4FF499A2 (Unity) GfxDevice::InsertCustomMarkerCallback
0x00007FFE51999BD1 (Unity) GfxDeviceWorker::RunCommand
0x00007FFE519A257C (Unity) GfxDeviceWorker::RunExt
0x00007FFE519A26AF (Unity) GfxDeviceWorker::RunGfxDeviceWorker

Comments (1)

  1. Siko2035

    Jul 23, 2025 16:01

    How to ‘Force the Editor to launch with OpenGL as the graphics API fixes the 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.