Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
2022.2.X
Issue ID
HRB-52
Regression
Yes
[URP] Crash when applying shaders from other packages to GameObjects and changing Scriptable Render Pipeline Settings
How to reproduce:
1. Open the user-attached “UpgradeCrash.zip” project
2. Open the Graphics section of the Project Settings window (Edit → Project Settings → Graphics)
3. Assign the “New Universal Render Pipeline Asset” to the “Scriptable Render Pipeline Settings” section
4. Focus the Editor window
Expected results: No crash
Actual results: Crash
Reproducible with: 14.0.2 (2022.2.0a11), 14.0.3 (2022.2.0b2, 2023.1.0a1)
Not reproducible with: 10.9.0 (2020.3.37f1), 12.1.7 (2021.3.6f1), 13.1.8 (2022.1.10f1), 14.0.2 (2022.2.0a10), 15.0.0 (2023.1.0a2, 2023.1.0a4)
Reproduced on: macOS Monterey 12.0.1
Note:
- Reproducible on a new project
- Not reproducible with HDRP
- Shader from the ProBuilder package was used
Stackframes:
0x00007ff7212147ec (Unity) ScriptableBatchRenderer::ApplyShaderPass
0x00007ff721223c77 (Unity) RenderShadowCasterPartsSRPBatcher
0x00007ff7212242ff (Unity) ScriptableRenderLoopShadowsJob
0x00007ff72152a8c3 (Unity) GfxDevice::ExecuteAsync
0x00007ff7218048cc (Unity) GfxDeviceClient::ExecuteAsync
0x00007ff72122415b (Unity) ScheduleRenderJobs
0x00007ff721217636 (Unity) ExecuteDrawShadowsCommand
0x00007ff721217f01 (Unity) ScriptableRenderContext::ExecuteScriptableRenderLoop
0x00007ff72077bc99 (Unity) ScriptableRenderContext_CUSTOM_Submit_Internal_Injected
-
Resolution Note:
Bug is a dupplicate after investigation
https://unity.slack.com/archives/C06TQ82JY/p1661780208405539Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-1249
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
- Multiple errors appear when compiling a ShaderGraph shader's code in a specific project
- TextMeshPro memory leak occurs when reloading the scene using Addressables
- Vector3 node has no X, Y, Z outputs when adding Vector3 node in the Visual Effect Graph
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
This is a duplicate of issue #UUM-1249