Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.4.0b17
Issue ID
797906
Regression
No
[command buffers] Crash related to shader code not handling null values properly
- Import the attached project
- Make sure editor_tool_sceen.unity is the opened scene
- On the Main Camera make sure the SSSAO component is enabled
- On that component change Visualization to View Bleeding
- Reset all component values to their default (using the Reset option from the context menu of the component)
- Disable the component
Unity crashes!
This case looks very similar to http://issuetracker.unity3d.com/issues/passing-null-to-materialeditor-dot-getmaterialproperties-crashes-at-pptr-operator-shader-star-ptr64 which is already fixed. This one crashes in older Unity versions as well
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Add comment