Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.3.X, 2019.1.X
Votes
0
Found in
2018.3.0b7
2018.3.4f1
Issue ID
1125427
Regression
Yes
[IL2CPP] System out of Memory exception is thrown if ScriptableObject is loaded from inside a DLL
To reproduce:
1. Download attached project “ReproduceSOLoadCrash 2.zip" and open in Unity
2. Open "SampleScene" scene
3. Enter to Play mode
4. Observe that within the Console "Logger settings loaded" message is printed
5. Change Platform to Standalone, iOS or Android
6. Change Scripting Backend to IL2CPP
7. Build and Run project
Expected results: Player does not Crash after Splash Screen
Actual results: Player Crashes after Splash Screen and throws "System out of memory" exception
Notes:
- This issue appears on Windows Standalone, macOS Standalone, iOS, and Android (IL2CPP)
- This issue does not appear on Editor
- This issue does not appear if Scripting Backend is Mono
Reproduced on Unity 2018.3.0b7, 2018.3.5f1, 2019.1.0b3 and 2019.2.0a4
Not reproduced on Unity 2018.2.20f1 and 2018.3.0b6
Regression on Unity 2018.3.0b7
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
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
Resolution Note (fix version 2019.2):
Work around this issue by adding a link.xml file with the following contents to the Assets/ folder of the project:
<linker>
<assembly fullname="core-logger-unity" preserve="all"/>
</linker>
This will prevent the managed code stripper from incorrectly removing managed bytecode from the core-logger-unity.dll assembly. This incorrect code removal is the source of the problem.