Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X
Votes
1
Found in
2022.3.17f1
2023.2.4f1
2023.3.0b1
6000.0.0b11
6000.1.0a7
7000.0.0a1
Issue ID
UUM-59760
Regression
No
Memory leak when using SerializeReference in IL2CPP Build
How to reproduce:
1. Open the attached project "SerializeReference MemLeak.zip"
2. Build And Run the project
3. Open the Memory Profiler in the Editor (Window>Analysis>Memory Profiler)
4. Change the "Target Selection" in the Memory Profiler to "WindowsPlayer"
5. Click on the "Capture New Snapshot" button
6. In the Player press space on the keyboard several times
7. Repeat step 5
8. In the Memory Profiler open the "Compare Snapshots" tab
9. Select both snapshots to compare
10. Switch to the "All Of Memory" tab
11. Select Native>Unity Subsystems>Objects
Expected results: The count of "<No Name>" Objects are the same in both snapshots
Actual results: The count of "<No Name>" Objects is larger in the second snapshot
Reproducible with: 2022.3.17f1, 2023.2.4f1, 2023.3.0b1
Could not test with: 2021.3.34f1 (no "All Of Memory" support in Memory Profiler)
Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Add comment