Search Issue Tracker
Won't Fix
Votes
1
Found in
2022.3.17f1
2023.2.4f1
2023.3.0b1
6000.0.0b11
6000.1.0a7
6000.2.0a1
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
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
- Foldout arrow indent is misaligned in the Inspector when used in Custom Type
- [Android] The Player screen turns black when playing a video under certain conditions
- Search window icons at the bottom are cut off when Search window is resized vertically
- "Try something else?" text label is cut off when searching for a long text in the Search window
- Rendering Debugger window sections do not have a minimum width set when resizing with the slider in the middle of the window
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.