Search Issue Tracker
Fixed in 2022.2.5f1
Fixed in 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a1
Votes
3
Found in
2022.1.24f1
2022.2.1f1
2023.1.0a23
2023.2.0a1
Issue ID
UUM-21880
Regression
Yes
IL2CPP build crashes when capturing memory snapshot
Reproduction steps:
- Open the attached project “BuildCrash“
- Press File>Build And Run
- Press Window>Analysis>Memory Profiler
- In the Memory Profiler window press Editor>Local>Windows Player>Select current build
- In the Memory Profiler window press Capture
Expected result: Memory Profiler successfully captures memory snapshot
Actual result: Build crashes
Reproducible with: 2022.1.0a16, 2022.1.24f1, 2022.2.1f1, 2023.1.0a23
Not reproducible with: 2020.3.42f1, 2021.3.15f1
Couldn't test with: 2022.1.0a15(The type or namespace name 'MultiColumnTreeView' could not be found)
Reproducible on: Windows 11
Note: Build crashes only if the “File>Build Settings>Script Debugging” option is selected
First lines of the stack trace:
0x00007FFE640EA84A (GameAssembly) [C:\Program Files\Unity\2022.1.24f1_709dddfb713f_x64\Data\il2cpp\libil2cpp\os\Win32\Assert.cpp:12] il2cpp_assert
0x00007FFE641495F5 (GameAssembly) [C:\Program Files\Unity\2022.1.24f1_709dddfb713f_x64\Data\il2cpp\libil2cpp\vm\Class.cpp:623] il2cpp::vm::Class::GetValueSize
0x00007FFE64075AEA (GameAssembly) [C:\Program Files\Unity\2022.1.24f1_709dddfb713f_x64\Data\il2cpp\libil2cpp\metadata\FieldLayout.cpp:101] il2cpp::metadata::FieldLayout::GetTypeSizeAndAlignment
0x00007FFE64076AF1 (GameAssembly) [C:\Program Files\Unity\2022.1.24f1_709dddfb713f_x64\Data\il2cpp\libil2cpp\metadata\FieldLayout.cpp:162] il2cpp::metadata::FieldLayout::LayoutFields
0x00007FFE6414BABF (GameAssembly) [C:\Program Files\Unity\2022.1.24f1_709dddfb713f_x64\Data\il2cpp\libil2cpp\vm\Class.cpp:985] il2cpp::vm::LayoutFieldsLocked
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
- Diagnostics logs are missing, duplicated, or out of order when viewing Player sessions in Cloud Diagnostics
- Prefab Overrides “Apply” button is too big and overlaps with the context menu’s outline
- Prefab Overrides “No Overrides” text is too large, and the the Context Menu of the Parent GameObject has a lot of empty space when opened
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
Resolution Note (fix version 2023.1):
A fix has been applied to il2cpp to address the issue.