Search Issue Tracker
Fixed in 2021.1.X
Votes
2
Found in
2019.3.8f1
2019.4
2020.2
Issue ID
1237886
Regression
No
RuntimeInitializeOnLoadMethod causes ExecutionEngineException error to be thrown in Player
How to reproduce:
1. Open the attached "EmptyRamTest.zip" project
2. Build to Standalone (make sure that Development Build is checked to see the error)
Expected result: No RuntimeInitializeOnLoadMethod errors are thrown in Build
Actual result: RuntimeInitializeOnLoadMethod causes "ExecutionEngineException" error to be thrown in Build
Reproducible with: 2019.4.2f1, 2020.1.0b14, 2020.2.0a15
Notes:
- Full error "ExecutionEngineException: Attempting to call method 'ETGgames.Utils.SingletonMono`1::get_Instance' for which no ahead of time (AOT) code was generated"
- Managed to reproduce in Mono and IL2CPP
- Reproducible in Standalone and UWP
- Could not reproduce on 2018.4 because of an error related to "RuntimeInitializeLoadType"
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 2021.1):
Fixed in: 2021.2.0a12, 2022.1.0a7