Search Issue Tracker

Fixed in 2.0.0

Votes

0

Found in [Package]

1.4.1

Issue ID

1340464

Regression

No

[Android] Memory allocations created every frame/update in Mobile Notifications

Package: Mobile Notifications

-

Reproduction steps:
1. Open the attached project: "Mobile Notification Ticket.zip"
2. Open the SampleScene
3. In the Build Settings enable Autoconnect Profiler
4. Build and Run
5. In the Profiler look for AndroidReceivedNotificationMainThreadDispatcher.Update()

Expected result: No additional memory is allocated when adding objects to s_ReceivedNotificationList
Actual result: List'1.AddRange() allocates memory when s_ReceivedNotificationList.AddRange(s_ReceivedNotificationQueue) is called

Reproducible with: 1.3.0 (2019.4.29f1), 1.4.1 (2020.3.14f1, 2021.1.15f1, 2021.2.0b4, 2022.1.0a2)

Reproducible with:
VLNQA00277, Asus ROG Phone, Android: 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00030, Lge LG G2, Android: 4.4.2, CPU: Snapdragon 800 MSM8974, GPU: Adreno (TM) 330
VLNQA00006, Samsung Galaxy S7, Android: 8.0.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
VLNQA00121, Samsung Galaxy S9, Android: 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72

Notes:
- Possible fix:
while (s_ReceivedNotificationQueue.Count > 0) {
s_ReceivedNotificationList.Add(s_ReceivedNotificationQueue.Dequeue());
}

  1. Resolution Note (fix version 2.0.0):

    Fixed in: 2.0.0 (available from 2019.4.0f1 and up)

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.