Search Issue Tracker
Fixed
Fixed in 6000.3.16f1, 6000.4.7f1, 6000.5.0b8, 6000.6.X
Won't Fix in 6000.6.X
Votes
0
Found in
6000.3.11f1
6000.4.0f1
6000.5.0a9
6000.6.0a1
Issue ID
UUM-137255
Regression
No
Crash on CreateResourceWithTag when rendering Custom Lighting ShaderGraph material while Forward+ is enabled and Keep Lighting Variants is disabled
How to reproduce:
1. Open the attached “IN-137163” project
2. Open the “New Shader Graph” located in the Assets folder
3. Uncheck the “Keep Lighting Variants“ box
4. Navigate open the “PC_Renderer” in the Inspector (Assets > Settings)
5. Change the Rendering Path to “Forward+”
6. Click on the Shader Graph tab and move around
7. Observe the crash
Reproducible with: 6000.3.11f1, 6000.4.0f1, 6000.5.0a9, 6000.6.0a1
Not reproducible with: 6000.0.71f1 (no “Keep Lighting Variants” option)
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
- The Editor freezes for ~3 minutes before the crash occurs
- Not reproducible with DX11 or Vulkan
First few lines of the stack trace:
0x00007FFF7C9861E0 (Unity) CheckDeviceStatus
0x00007FFF7C96F314 (Unity) GfxDeviceD3D12::ReportResourceCreationError
0x00007FFF7C961735 (Unity) GfxDeviceD3D12::CreateResourceWithTag
0x00007FFF7C91DC79 (Unity) BufferD3D12::CreateBufferResource
0x00007FFF7C91FF59 (Unity) BufferD3D12::InitializeResource
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
- Crash on Scripting::ScriptingWrapperFor when exiting Play Mode during an active web request
- Material Inspector shortly disappears resulting in "Add Component" button jumping when the Material is recompiled
- Hand Interaction Profile breaks hand teleport to arbitrary locations
- Grabbing Dynamic Attach interactable in Interaction Simulator makes controller spin
- XRI Starter Assets Interactable shader generates Console warnings
Resolution Note:
Fixed in 6000.3.16f1
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (fix version 6000.6):
Fixed in 6000.3.16f1
Resolution Note (fix version 6000.5.0b8):
Fixed in 6000.5.0b8
Resolution Note (fix version 6000.4.7f1):
Fixed in 6000.4.7f1