Search Issue Tracker
Fixed in 1.3.1
Votes
0
Found in [Package]
1.3.0
Issue ID
1271866
Regression
No
[Mobile Notifications] AndroidReceivedNotificationMainThreadDispatcher allocates new list in every frame
In AndroidReceivedNotificationMainThreadDispatcher.cs line 27, a new AndroidJavaObject list is allocated on each frame.
Optimize the code so it would re-use the same collection to reduce GC calls.
Steps to reproduce:
1) Create a project that utilizes AndroidReceivedNotificationMainThreadDispatcher class.
2) Build and run on Android.
3) Monitor GC.Alloc calls coming from AndroidReceivedNotificationMainThreadDispatcher in Profiler.
Expected: Fewer list allocations are done.
Actual: List allocations done in each frame.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "InvalidOperationException" is thrown when clicking "Ctrl+Z" after opening Gradient Editor
- Breadcrumbs don't change names when graphs are renamed
- Adaptive Probe Volumes require a second bake for correct probe lighting data when Min Probe Spacing is changed in URP
- GUI Skin Asset dropdowns show expanded arrow icon but do not display content when opened with arrow keys
- Seams are visible in reflective surfaces when using box projection in Android Build Profile
Add comment