Search Issue Tracker
By Design
Votes
0
Found in
2022.3.66f1
6000.0.57f1
6000.2.5f1
6000.3.0b2
6000.4.0a1
Issue ID
UUM-117549
Regression
No
Memory leak when running tests in IL2CPP with System.Threading.Timer
How to reproduce:
1. Open the “IN-111094.zip“ project
2. Open Window → General → Test Runner
3. Open the ‘Player’ section
4. Run all the tests on a Standalone build
5. Open the Windows Task Manager and observe the Memory field of the build
Expected result: Memory doesn’t go over 1GB most of the time (or some other bearable memory usage)
Actual result: Memory goes >15 GB (or other worse memory usage)
Reproducible in: 2022.1.0b1 (ea0f0219deed), 2022.3.66f1, 6000.0.57f1, 6000.2.5f1, 6000.3.0b2
Not reproducible in: 2022.1.0a16
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
Notes:
- Typically, memory used in ‘reproducible' versions ranges between 15 and 50 GB, while in 'Not reproducible’ versions it is up to 1 GB
- In Mono, this issue is not reproducible
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
- Palette Settings link to the documentation isn’t working
- Tags & Layers window has inconsistent remove button behaviour between Tags, Sorting Layers, and Rendering Layers when there are no removable items in the list
- "Type Options" and "Node Library" dropdowns do not open when clicked on the title
- Public char variables uneditable in Inspector when project setting "Use IMGUI Default Inspector" is enabled
- IAP Listener component’s list titles go out of bounds when resizing the Inspector window horizontally
Resolution Note:
There was no a memory leak in this use case. The repro caused a huge number of timers callbacks to be queue creating a GC allocation spike.