Search Issue Tracker
Fixed in 2.0.0
Votes
0
Found in [Package]
1.4.2
Issue ID
1396201
Regression
No
[Android] Mobile Notifications package generates GC per every frame
Reproduction steps:
1. Open the attached project "MobileNotificationAndroidGCIssue-2021.2.zip"
2. Select the Autoconnect Profiler and Build on an Android device
3. Observe the Profiler
Expected result: GC is not generated
Actual result: GC is generated every frame
Reproducible with: 1.4.1(2019.4.35f1), 1.4.2(2020.3.29f1, 2021.2.12f1, 2022.1.0b9, 2022.2.0a5)
Not reproducible with: 2.0.0(2020.3.29f1, 2021.2.12f1, 2022.1.0b9, 2022.2.0a5)
Reproducible with these devices:
----------, Huawei - (ELS-NX9), Android 10, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00264, Samsung Galaxy S10+ (SM-G975F), Android 10, CPU: NOT FOUND, GPU: Mali-G76
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2.0.0):
Fixed in Mobile Notifications 2.0.0 available in 2019.4 and above