Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.34f1
Issue ID
UUM-1908
Regression
No
[Backport] Excessive IL2CPP Stripping of [RuntimeInitializeOnLoadMethod] method with [Preserve] causes crash on runtime
How to reproduce:
1. Open the attached "UWP_StrippingExcessive.zip" project
2. Make sure that "Script changes while playing" has "Stop Playing and Recompile" option chosen in Preferences Settings
3. Build to UWP
4. Open the Visual Studio Solution file, located in the built project's directory
5. Build the Solution on Local Machine with Debug and x64 options
Expected results: The build does not crash when doing excessive IL2CPP stripping of \[RuntimeInitializeOnLoadMethod] method with \[Preserve]
Actual results: The build crashes when doing excessive IL2CPP stripping of \[RuntimeInitializeOnLoadMethod] method with \[Preserve]
Reproducible with: 2019.3.14f1, 2019.1.0b9, 2020.2.0a11
Notes:
- Could not reproduce on 2018.4, because of errors
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
There are no fixes planned for this Bug