Search Issue Tracker
Duplicate
Votes
0
Found in
6000.0.23f1
6000.1.0a7
6000.2.0a1
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)
-
Resolution Note:
null
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-86520
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
This is a duplicate of issue #UUM-86520