Search Issue Tracker
In Progress
Under Consideration for 6000.0.X, 6000.1.X
Votes
0
Found in
6000.0.23f1
6000.1.0a7
Issue ID
UUM-86296
Regression
No
GraphicsStateCollection::GetVariants() Crash when the Collection contains Shaders with the exact same Keywords
*+Description+*
GraphicsStateCollection::GetVariants() causes Editor to crash with memory allocation error. More info can be found here: https://discussions.unity.com/t/in-87175-graphicsstatecollection-tracing-causes-crash/1540747
*+Initial setup+*
Unity 6000.0.23
*+Reproduction steps+*
Issue is not specific to a particular project and can be reproduced with any scene.
* First download the attached GraphicsVariantsScriptTest.cs script along with the two graphicsstate files (Test1.graphicsstate & Test2.graphicsstate).
* Create an empty scene object and attach the script.
* Drag Test1.graphicsstate to the script's empty "test" variable
* Click on the "Update collection list" button from the script's options menu
*+Expected behaviour+*
No fatal errors when calling GraphicsStateCollection::GetVariants()
*+Actual behavior+*
Editor crashes due to invalid memory allocation size.
*+Logs and Links+*
(Add links to Yamato jobs, links to logs, and add a stack trace in this section)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
- Crash on EditorApplication:Internal_CallUpdateFunctions when pushing property block by index to SpriteShapeRenderer
- Depth Texture Mode "After Opaques" breaks when "Full Screen Pass Renderer Feature" is added
Add comment