Search Issue Tracker
Fixed in 2023.1.10f1
Fixed in 2022.3.X, 2022.3.7f1, 2023.1.X, 2023.2.X, 2023.3.X, future release
Votes
1
Found in
2022.3.5f1
Issue ID
UUM-43158
Regression
Yes
MARSHAL.OFFSETOF fails to calculate the correct offset of property within Explicit layout with FieldOffset
Steps to reproduce:
1. Open the attached user project " SampleUnityIL2CppBug.zip"
2. Open the Build Settings window and make sure that SampleScene is in the list of scenes
3. Make an IL2CPP development build with Autoconnect Profiler enabled
4. Observe the result in the Editor Console "(offs (value) 12 - 12)"
5. Open the attached project on Unity 2022.3.4 and repeat the steps above
6. Observe the result in the Editor Console "(offs (value) 12 - 16)"
Expected results: MARSHAL.OFFSETOF calculates the correct offset of property within Explicit layout with FieldOffset
Actual Results: MARSHAL.OFFSETOF fails to calculate the correct offset of property within Explicit layout with FieldOffset
Reproducible in: 2022.2.0a7, 2022.3.5f1, 2023.1.5f1, 2023.2.0b1, 2023.3.0a1
Not reproducible: 2021.3.28f1, 2022.2.0a5
Couldn't test on 2022.2.0a6 due to this error "GfxDeviceD3D11Base::WaitForLastPresentationAndGetTimestamp()" when building the Player and launching it
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Player crash when switching focus in Exclusive Fullscreen mode with DirectX 12
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
Add comment