Search Issue Tracker
Active
Under Consideration for 6000.4.X
Votes
0
Found in
6000.2.9f1
6000.3.0b7
6000.4.0a4
Issue ID
UUM-125632
Regression
No
Crash on TexturesD3D12::UploadTextureSubData2D when importing a specific asset
Reproduction steps:
1. Open the attached project “IN-118423_BOOM.zip”
2. Observe the crash
Alternatively:
1. Open the attached project “IN-118423_BOOM.zip”
2. In the Project window, right click in the “Assets” folder and “Reimport All”
3. Observe the crash
Reproducible with versions: 6000.2.9f1, 6000.3.0b7, 6000.4.0a4
Couldn't test with versions: 6000.0.60f1 (due to the project breaking into a unusable state when downgrading below the user’s original version (6000.1.14f1))
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
-First reproduction steps are for the Editor crashing during the initial start up, secondary steps are for consistently reproducing the crash after reimporting all assets from the Project window. Both crashes are related to the “Vase_Prefab” asset;
-Not reproducible on DirectX11 and Vulkan;
-The project no longer crashes if you delete the “Vase_Prefab” from Assets\Models\Props\Vase, however, reimporting only the “Vase_Prefab” alone does not trigger the crash;
-Crash is inconsistent and may require reimporting all assets twice in a row to reproduce.
First few lines of stacktrace from the initial launch crash:
0x00007FFE46634A91 (Unity) GfxDeviceD3D12Base::BeginProfileEvent
0x00007FFE47DDBE9A (Unity) GfxDeviceWorker::RunCommand
0x00007FFE47DDE43C (Unity) GfxDeviceWorker::RunExt
0x00007FFE47DDE56F (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FFE46277E5E (Unity) Thread::RunThreadWrapper
First few lines of stacktrace from the alternative reproduction steps crash:
0x00007FFE5238D6DD (Unity) TexturesD3D12::UploadTextureSubData2D
0x00007FFE5235578E (Unity) GfxDeviceD3D12::UploadTextureSubData2DImpl
0x00007FFE52081E56 (Unity) GfxDevice::UploadTextureSubData2D
0x00007FFE53AD3C29 (Unity) GfxDeviceWorker::RunCommand
0x00007FFE53ADE43C (Unity) GfxDeviceWorker::RunExt
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment