How to reproduce:
1. Open the attached “IN-11978.zip” project
2. Open the “SampleScene”
3. Open the “crash_text.txt” file
4. Select all of the text and copy it
5. In the Editor, create an empty GameObject and select it
6. In the Inspector window, paste the copied block of text into the GameObject’s name field
7. Resize the Inspector window for a while
8. Observe the crash

Reproducible in: 6000.0.1f1, 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a2
Not reproducible in: 6000.0.0f1

Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested

First few lines of stacktrace:
0x00007FFD25567FBF (Unity) PPtr<Shader>::operator Shader * __ptr64
0x00007FFD25B1B48D (Unity) Material::GetShader
0x00007FFD262A164D (Unity) GUIStyle::RenderText
0x00007FFD2629DF65 (Unity) GUIStyle::DrawContent
0x00007FFD25100A01 (Unity) GUIStyle_CUSTOM_Internal_DrawContent

Notes:
- IndexOutOfRange and InvalidOperation exceptions are visible in the console prior to crashing
- It might take some time to get the Editor to crash. Just keep resizing the Inspector and selecting/deselecting the GameObject. Shouldn’t take more than around a minute.
- Issue is reproducible in any project

Additional version testing comments:
- 2023.1.0a1: Nothing happens after repro steps
- 2023.2.0a1: Editor becomes sluggish after repro steps
- 6000.0.0f1: Editor does not crash, but gets stuck in a constant code execution loop after repro steps