Search Issue Tracker
Fixed
Fixed in 6000.0.58f1, 6000.2.5f1, 6000.3.0b1
Votes
5
Found in
6000.0.56f1
6000.1.16f1
6000.2.1f1
6000.3.0a5
Issue ID
UUM-104855
Regression
Yes
[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.0.56f1, 6000.1.16f1, 6000.2.0a4, 6000.2.1f1, 6000.3.0a5
Not reproducible with: 2023.1.0a1, 6000.2.0a3
Reproducible on: Windows 10 (22H2) (user's), Windows 11 (24H2) (user's)
Not reproducible on: No other environments tested
Notes:
- 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)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Siko2035
Jul 23, 2025 16:01
How to ‘Force the Editor to launch with OpenGL as the graphics API fixes the issue’ ?