Search Issue Tracker
Fixed
Fixed in 2021.3.28f1, 2022.2.21f1, 2023.1.0b18, 2023.2.0a15
Votes
1
Found in
2021.3.24f1
2022.2.17f1
2023.1.0b13
2023.2.0a12
Issue ID
UUM-33942
Regression
No
Blittable classes are not being pinned and passed directly to the native code when using IL2CPP Scripting Backend
How to reproduce:
1. Open the "IN_38621" project
2. Press File -> Build Settings -> Build
3. In the build folder open the "Il2CppOutputProject\Source\Assembly-CSharp.cpp" script
Expected result: blittable classes are pinned and passed directly to the native code
Actual result: generated code creates a marshalled object on the stack and passes a pointer to the native code
Reproducible with: 2021.3.16f1, 2021.3.24f1, 2022.2.17f1, 2023.1.0b13, 2023.2.0a12
Not reproducible with: 2020.3.47f1, 2021.3.15f1
Testing environment: Windows 10 Pro
Notes:
- Also reproducible on Android
- Not reproducible on WebGL
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
cgrigoras
Nov 29, 2023 14:32
We're pretty certain this fix breaks our game and prevents us from upgrading Unity version, more details here: https://forum.unity.com/threads/il2cpp-class-object-interop-marshalling-fails.1521271/