How to reproduce:
1. Open the “il2cppAccessViolationCrash” project
2. Open the “SampleScene”
3. Make sure that the “Scripting Backend” is set to “IL2CPP” (File > Build Settings > Player Settings > Other Settings > “Configuration”)
4. Build And Run

Expected result: The Player does not crash and the “ExecutionEngineException” exception is logged to Player.log
Actual result: The Player crashes

Reproduced with: 2021.1.0a1, 2021.3.35f1, 2022.3.20f1, 2023.2.11f1, 2023.3.0b8
Not reproduced with: 2020.2.0a21

Reproduced on: Windows 11
Not reproduced on: No other environment tested

Notes:
1. Not reproducible with “Mono” Scripting Backend
2. Not reproducible in the Editor

First few lines of the stack trace:
0x00007FF8043A7596 (GameAssembly) [C:\UnitySrc\2023.3.0b8\Editor\Data\il2cpp\libil2cpp\vm\Runtime.cpp:625] il2cpp::vm::Runtime::InvokeWithThrow
0x00007FF8043A7039 (GameAssembly) [C:\UnitySrc\2023.3.0b8\Editor\Data\il2cpp\libil2cpp\vm\Runtime.cpp:610] il2cpp::vm::Runtime::Invoke
0x00007FF8043A7423 (GameAssembly) [C:\UnitySrc\2023.3.0b8\Editor\Data\il2cpp\libil2cpp\vm\Runtime.cpp:872] il2cpp::vm::Runtime::InvokeConvertArgs
0x00007FF8043A70B2 (GameAssembly) [C:\UnitySrc\2023.3.0b8\Editor\Data\il2cpp\libil2cpp\vm\Runtime.cpp:665] il2cpp::vm::Runtime::InvokeArray
0x00007FF8043CBF5C (GameAssembly) [C:\UnitySrc\2023.3.0b8\Editor\Data\il2cpp\libil2cpp\icalls\mscorlib\System.Reflection\RuntimeMethodInfo.cpp:188] il2cpp::icalls::mscorlib::System::Reflection::RuntimeMethodInfo::InternalInvoke