Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
1
Found in
2021.3.30f1
2022.3.10f1
2023.2.0b8
2023.3.0a6
Issue ID
UUM-52900
Regression
No
Crash on TexturesD3D12::UploadTextureSubData2D when rendering a Custom Lit Shader
Reproduction steps:
1. Open the attached project “CrashRepro“
2. Select “Cube“ GameObject in the Hierarchy window
Expected result: "Cube" is selected
Actual result: Editor crashes
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.2.0b8, 2023.3.0a6
Couldn’t test with: 2023.1.14f1 - (broken shader)
Reproducible on: Windows 10
Not reproducible on: No other environment tested
First few lines of stack trace:
{noformat}
0x00007FF760424923 (Unity) TexturesD3D12::UploadTextureSubData2D
0x00007FF760449D85 (Unity) GfxDeviceD3D12::UploadTextureSubData2DImpl
0x00007FF7601CCEB8 (Unity) GfxDevice::UploadTextureSubData2D
0x00007FF761A1C78A (Unity) GfxDeviceWorker::RunCommand
0x00007FF761A249DB (Unity) GfxDeviceWorker::RunExt
0x00007FF761A24AF8 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FF7600E5BC7 (Unity) Thread::RunThreadWrapper
0x00007FF84BC57344 (KERNEL32) BaseThreadInitThunk
0x00007FF84D9E26B1 (ntdll) RtlUserThreadStart{noformat}
Note: Reproduces with all Graphics APIs
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
This issue is not API specific bug, nor a shader compiler issue. With the information currently available, this seems to be a bug in user shader code. If further information becomes available that points to an implementation bug, feel free to reopen this ticket.
Resolution Note (2023.3.X):
This issue is not API specific bug, nor a shader compiler issue. With the information currently available, this seems to be a bug in user shader code. If further information becomes available that points to an implementation bug, feel free to reopen this ticket.