Reproduction steps:
1. Open the attached “CrashRepro” project
2. Close the Unity Editor

Expected result: Unity Editor closes
Actual result: Unity Editor crashes

Reproducible with: 1.7.4, 1.8.2 (2021.3.13f1, 2021.3.15f1, 2022.1.21f1, 2022.1.24f1, 2022.2.0b13, 2022.2.1f1, 2023.1.0a15, 2023.1.0a22)
Not reproducible with: 1.7.3 (2020.3.42f1, 2021.3.15f1, 2022.1.24f1, 2022.2.1f1), 1.7.4, 1.8.2 (2020.3.42f1, 2021.3.12f1, 2022.1.0a1, 2022.1.20f1, 2022.2.0a1, 2022.2.0b12, 2023.1.0a1, 2023.1.0a14)

Reproducible on: Windows 11 Pro 22H2

First lines of the stack trace:

{noformat}0x00007FFE13D6FB3C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\mini\mini-runtime.c:3259] mono_jit_runtime_invoke
0x00007FFE13CAEB34 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\object.c:3066] do_runtime_invoke
0x00007FFE13CAECCC (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\object.c:3113] mono_runtime_invoke
0x00007FF754963B54 (Unity) scripting_method_invoke
0x00007FF7549434A4 (Unity) ScriptingInvocation::Invoke{noformat}

Notes:

• As a workaround, move the project to a folder whose path doesn’t contain special characters
• Before closing the editor, there are a lot of “Assertion failed on expression: ‘exception == SCRIPTING_NULL’” errors in the Console