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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment