Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3
2019.3.0f5
2020.1
Issue ID
1212189
Regression
No
[IL2CPP] Standalone throws ExecutionEngineException when using generics (interface/struct) with MemoryRfReader
How to reproduce:
1. Open attached project with ILL2CPP Editor "ExecutionEngineException.zip"
2. Make sure that Api Compatibility Level is set to .NET 4.x (Edit -> Project Settings -> Player -> Api Compatibility Level)
3. Enable Development Build (File -> Build Settings -> Development Build)
4. Build and Run
5. Observe Standalone Console
Expected result: no errors are thrown, Standalone console window is not visible
Actual result: "'Realmforge.Evil.Serializers.TypeSerializer::Deserialize<Realmforge.Shared.MemoryRfReader>' for which no ahead of time (AOT) code was generated." is thrown
Reproducible with: 2019.3.0f5, 2020.1.0a20
Could not test with: 2017.4 (ILL2CPP was not yet released), 2018.4, 2019.2 ('UnsafeUtility' does not contain a definition for 'MemSet' error is thrown)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a24
Resolution Note (fix version 2019.3):
Fixed in: 2019.3.7f1