Search Issue Tracker
Fixed in 2020.1.X
Votes
3
Found in
2018.3.0f2
Issue ID
1119943
Regression
No
[Android] Memory is leaking on android device and Scripting Runtime Version is set to .Net 4.x Equivalent
How to reproduce:
1. Open attaches Unity project
2. Open Profiler window
3. Open build settings.
4. Select Development Build and Autoconnect Profiler
5. Build and run on a device
6. Click the "Init Dictionary Data" button
7. Click the "Test Alloc Local Memory" button for several times
--In the Profiler Window notice, that memory usage raises
Reproduced with: 2019.2.0a2, 2019.1.0b1, 2018.3.3f1, 2017.4.19f1.
Devices under test:
Reproduced on:
VLNQA00136, Samsung Galaxy S9+ (SM-G965F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00257, Sony Xperia XZ Premium (G8141), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
Notes:
On 2018 and 2019 version memory usage raises from 15MB to ~400MB, on 2017.4 version memory usage fraises to ~30MB.
Building with mono or il2cpp backends lead to the same result
After setting Scripting Runtime Version to 3.5 memory usage raises to ~30MB
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
- The build size is larger when Models have Animation Type set to Generic
- Error "ArgumentException: Both 'ok' and 'cancel' strings are null or empty" logged when User is trying to create circular dependencies in UI Builder Hierarchy
- "SupportsRandomWriteOnRenderTextureFormat()" shows "False" when executed on 2023.2 and 6000.0 streams
Add comment