Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.3.7p3
Issue ID
896028
Regression
No
[Android] Calling Marshal.AllocHGlobal and then LoadAllAssets increases PSS memory more than the bundle being loaded
How to reproduce:
1. Open user attached project
2. Build and run
3. Wait for Marshall allocation and asset bundle load to finish
4. Compare the values of 'Before LoadAllAssets' and 'After LoadAllAssets' thread peaks
Expected behaviour: Memory usage to increase about 3MB
Actual behaviour: Memory usage increases 10 or more MB
Reproduced on: 5.3.7p3
Not reproduced on: 5.4.5f1, 5.5.3f1, 5.6.0f3, 2017.1.0b1
Devices under testing:
Reproduced on:
Samsung Galaxy S7 | Exynos 8890 | Mali-T880 | Android 7.0
Samsung Galaxy S7 Edge | Exynos 8890 | Mali-T880 | Android 7.0
Samsung Galaxy S5 Neo | Exynos 7580 | Android 6.0.1
Xaomi Mi 5s | Qualcomm Snapdragon 821 | Adreno 530 | Android 6.0.1
LG Nexus 5X | Qualcomm Snapdragon 808 | Adreno 330 | Android 7.1.2
LG Nexus 5 | Qualcomm Snapdragon 800 | Adreno 418 | Android 6.0.1
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