Search Issue Tracker
By Design
Votes
0
Found in
2017.3.1p4
Issue ID
1029183
Regression
No
[IL2CPP] WeakReference causes memory leak in .NET 3.5 builds
Steps to reproduce:
1. Open user attached project
2. Build and Run IL2CPP .NET 3.5 build on your device
3. Tap "Test 1" and notice Mono memory going up to 150 in the profiler
4. Tap "Set null" and notice that Mono memory is not cleaned
Expected result: When "Set Null" is set Mono memory should be cleaned
Reproduced in: 2018.2.0b4, 2018.1.0f2, 2017.4.3f1, 2017.3.1p4, 2017.2.3f1, 2017.1.3p2
Tested with:
LGE Nexus 5, OS Version 6
Samsung Galaxy S5 Mini, OS Version 6
HTC One Mini, OS Version 4
iPhone 7 iOS 11.0
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment