Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.14f1
Issue ID
1096821
Regression
No
[Android] Massive SpriteRenderer.MultipleRender spikes on some Android devices
Steps to reproduce:
1. Open user attached project
2. Build and Run to an Android device
3. Profile the game and observe the frequent SpriteRenderer.MultipleRender spikes under BatchRenderer.Flush
Expected result: SpriteRenderer.MultipleRender should not cause ms spikes on some devices
Reproduced in: 2018.3.3f1, 2018.2.14f1, 2018.2.0b1
Tested devices:
Reproduced:
VLNQA00140, Samsung Galaxy S4 (GT-I9505), Android 5.0.1, CPU: Snapdragon S4 Plus MSM8960, GPU: Adreno (TM) 320 - most noticeable
VLNQA00030, Lge LG G2 (LG-D802), Android 4.4.2, CPU: Snapdragon 800 MSM8974, GPU: Adreno (TM) 330
VLNQA00126, Samsung Galaxy S5 mini (SM-G800F), Android 6.0.1, CPU: Exynos 3 Quad 3470, GPU: Mali-400 MP
VLNQA00078, Motorola Nexus 6 (Nexus 6), Android 7.1.1, CPU: Snapdragon 805 APQ8084AB, GPU: Adreno (TM) 420 - not frequent, but spikes are present
VLNQA00032, Motorola Moto X (2nd Gen) (XT1092), Android 5.1, CPU: Snapdragon 801 MSM8974AC, GPU: Adreno (TM) 330 - not frequent, but spikes are present
VLNQA00106, Samsung Galaxy S2 Plus (GT-I9105P), Android 4.2.2, CPU: Broadcom BCM28155, GPU: VideoCore IV HW
Not reproduced:
VLNQA00108, Lge LG Leon 4G LTE (LG-H340n), Android 5.0.1, CPU: Snapdragon 410 MSM8916, GPU: Adreno (TM) 306
VLNQA00001, Google Pixel 2 (Pixel 2), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00136, Samsung Galaxy S9+ (SM-G965F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2018.4.X):
Won't fix: partially caused by different priorities of main and render threads, changing priorities can regress performance in other areas.