Search Issue Tracker
Fixed
Fixed in 6000.0.38f1, 6000.1.0b6, 6000.2.0a1
Votes
0
Found in
6000.0.25f1
6000.1.0a3
6000.2.0a1
Issue ID
UUM-86520
Regression
No
Crash on GraphicsStateCollection::KeywordsFromShaderAndKeywordNames when calling GraphicsStateCollection.GetVariants()
Reproduction steps:
1. Open the “ASDQWE” project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. In the Hierarchy Window, select the “Test“ GameObject
4. In the Inspector Window, click on the "Update collection list" button from the GraphicsVariantsScriptTest Script options menu
5. Observe the Editor
Expected result: No fatal errors occur when calling GraphicsStateCollection::GetVariants()
Actual result: The Editor crashes due to invalid memory allocation size.
Reproducible with: 6000.0.25f1, 6000.1.0a3
Could not test with: 2021.3.45f1, 2022.3.52f1 (The GraphicsStateCollection is not available in this stream)
Reproducible on: MacOS 14.6.1 Intel, Windows 10 (user’s)
Not reproducible on: No other environment tested
Note: A user reported using the same GraphicsStateCollection during each level to load, warmup, trace, and save solves this issue
First few lines of the stack trace (Windows):
{noformat}0x00007FF8C845B699 (KERNELBASE) RaiseException
0x00007FF84D9F0C52 (Unity) LaunchBugReporter
0x00007FF84D2B9B7F (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FF84D2BA67A (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FF84DF6915D (Unity) DebugStringToFilePostprocessedStacktrace{noformat}
First few lines of the stack trace (MacOS):
{noformat}#0 0x0000010cc295a2 in GraphicsStateCollection::KeywordsFromShaderAndKeywordNames(Shader const*, core::basic_string<char, core::StringStorageDefault<char>> const&, core::vector<LocalKeywordInfo, core::allocator<LocalKeywordInfo, 0ul>>&) const
#1 0x0000010cc2929b in GraphicsStateCollection::GetVariants(core::vector<ShaderVariant, core::allocator<ShaderVariant, 0ul>>&) const
#2 0x0000010c6edd70 in GraphicsStateCollection_CUSTOM_GetVariants(void*, ScriptingBackendNativeArrayPtrOpaque*)
#3 0x0000016f2c7382 in (wrapper managed-to-native) UnityEngine.Experimental.Rendering.GraphicsStateCollection:GetVariants_Injected (intptr,UnityEngine.Experimental.Rendering.GraphicsStateCollection/ShaderVariant[]) [{0x7fab1ca9d0f8} + 0xa2] (0x16f2c72e0 0x16f2c7437) [0x15fec4a80 - Unity Child Domain]
#4 0x0000016f24f270 in (wrapper runtime-invoke) object:runtime_invoke_void__this__ (object,intptr,intptr,intptr) [{0x7fabaa882b98} + 0x180] (0x16f24f0f0 0x16f24f490) [0x15fec4a80 - Unity Child Domain]{noformat}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Assertion failed on expression” errors thrown when undoing Nodes creation with keyboard shortcut
- Crash on various stack traces when using Texture2D.CreateExternalTexture() while rendering
- Clicking on section text in Node Library > Context folder throws NullReferenceException errors
- Node Library window sections text in Context folder are not visible when Editor is set to Light Theme
- "Scene Depth Difference" Node has an input Port which is called Position WS, directly referring to the World Space Position, when only the View Space Position can reflect if the object's depth is below or above the Plane
Add comment