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
- [RenderGraph] Outputs from camera stack override each other when using OpenGLES3 with a custom renderer feature
- An "RefreshInternalV2 is called before InitialRefresh" error is thrown when opening a project where a build profile with Player settings added is selected
- MeshCollider preview gizmo disappears from the Scene view when overriding the mesh asset using any 3D editing tool
- Tutorial project is not created when started from the Get set up tab
- Audio Listener Component expands when selected
Add comment