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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment