Search Issue Tracker
Won't Fix
Votes
1
Found in
2020.3.32f1
2021.2.15f1
2022.2.0a8
Issue ID
UUM-3652
Regression
No
[Android] EventSystem.Update() causes GC.Alloc on either quickly tapping the screen or interacting with UI components
Reproduction steps:
1. Open the user's attached project "Test.zip"
2. Add a UI component ("Slider", "Button" etc.) to the Canvas
3. Enable "Deep Profiling" and "Autoconnect Profiler"
4. Build for Android
5. Inspect the Profiler and tap on the screen with quick successions or interact with the UI Component
Expected result: EventSystem.Update() does not cause GC.Alloc on either quickly tapping the screen or interacting with UI components
Actual result: EventSystem.Update() causes GC.Alloc on either quickly tapping the screen and increasing the GC.Alloc by 320B or interacting with UI components cause GC.Alloc to increase by 1.7Kb
Reproduces on: 2019.4.36f1, 2020.3.32f1, 2021.2.15f1, 2022.1.0b11, 2022.2.0a8
Reproduces on these devices:
VLNQA00013 - Galaxy S6 Edge+ (SM-G928F), CPU: Exynos 7 Octa (7420), GPU: Mali-T760, OS: 7.0.0
VLNQA00317 - Vivo NEX 3 5G (V1924A), CPU: Snapdragon 855+, GPU: Adreno 640, OS: 9.0.0
N/A, Google Pixel 3 (Pixel 3), Android 12, CPU: Snapdragon 845, GPU: Adreno (TM) 630
VLNQA00413 - Samsung Galaxy Note10+ (SM-N975F), OS: 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
VLNQA00372 - Galaxy S21 5G (SM-G991U), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00202 - Samsung Galaxy Note 9 USA (SM-N9600), CPU: Snapdragon 845 SDM845, GPU: Adreno 630, OS: 9.0.0
VLNQA00177 - Xiaomi Mi Note 2 (Mi Note 2), OS: 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno 530
VLNQA00231 - HUAWEI Mate 20 Pro (LYA-L29), OS: 9.0.0, CPU: HiSilicon Kirin 980, GPU: Mali-G76
VLNQA00406 - Galaxy Z Flip3 5G (SM-F711B), OS: 11, CPU: Snapdragon 888, GPU: Adreno 660
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
User tested devices:
- Xiaomi Poco X3 (M2007J20CG) (Android 10)
- Sony Xperia XZ (F8331) (Android 8)
Notes:
-Issue does not reproduce on the Standalone Windows player
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
- Rigidbody2D.Slide API does not have the needed configuration when creating a 2D Top-Down character controller
- Opening reference for "Playables"component redirects to a missing page
- Sprite Renderer image is changed when switching Mask Interaction and changing Sprite to a shared Sprite
- An unsigned integer is not compared with an integer correctly in player when using IL2CPP backend
- Graphical artifacts are being rendered in Scenes that are loaded during run-time when GPU Resident Drawer is turned on
Resolution Note:
After investigation, we have deemed this a low priority issue that won't be fixed in the near future either because it is too costly to implement or because there are risks of introducing other problems doing so.
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.