Search Issue Tracker

Fixed

Votes

0

Found in [Package]

1.0.0

Issue ID

PROFB-70

Regression

No

Crash on scripting_array_length when selecting <No Name> object in Memory Profiler

Package: Memory Profiler

-

Reproduction steps:
1. Open the attached “CrashRepro” project
2. Click Window > Analysis > Memory profiler
3. Import the attached snapshot “CrashSnapshot”
4. Click “All Of Memory”
5. Click “Scripting Memory” > “TMPro.TMP_GlyphPairAdjustmentRecord[]”
6. Click “<No Name>"

Expected result: Object opens in Memory Profiler
Actual result: Unity Editor crashes

Reproducible with: 1.0.0 (2023.1.0a20)

Reproducible on: Windows 10

First lines of the stack trace:
0x00007FFF8131DC0E (Unity) scripting_array_length
0x00007FFF819157D3 (Unity) TextRendering::TextCoreGeneratorGroup::Get
0x00007FFF8195BDCF (Unity) GUIStyle::DrawContent0x00007FFF806EFED0 (Unity) GUIStyle_CUSTOM_Internal_DrawContent_Injected
0x000002B1DDB73686 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.GUIStyle:Internal_DrawContent_Injected (UnityEngine.GUIStyle,UnityEngine.Rect&,UnityEngine.GUIContent,bool,bool,bool,bool,bool,bool,UnityEngine.Vector2&,UnityEngine.Vector2&,UnityEngine.Color&,UnityEngine.Color&,UnityEngine.Color&,single,single,single,single,bool,bool)

Note: Couldn’t reproduce this locally

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.