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
- Camera.allCameras returns cameras from all loaded Scenes when using multi-Scene setup
- Camera.layerCullDistances has no effect when GPU Resident Drawer is enabled
- ARM64 and ARMv7 APKs return the same version code when "Split APKs by target architecture" is enabled
- Crash on ProfilerMutexLock when closing a project with specific Assets
- “Callback unregistration failed. Callback not registered.” is thrown when changing layouts with two "Font Asset Creator" windows docked
Add comment