Search Issue Tracker
By Design
Votes
3
Found in
5.4.0f3
Issue ID
825754
Regression
Yes
[Android] EventSystem.Update() gives a big spike after first touch
Steps to reproduce:
1) Create a new project.
2) Add any UI element ( tested with Text and Image).
3) Enable Development Build and Autoconnect Profiler.
4) Build and run project on a device.
5) After game will be loaded, you will notice that EventSystem.Update() been loaded on the first frame (check profiler).
6) Click anywhere on the screen and you will notice that its been called again and takes a lot of memory (check profiler).(see attached image 'bug.png').
Expected result: EventSystem.Update() should not cause a big spike after screen been touched first time.
Actual result: It causes a big spike after screen been touched first time.
Reproduced with: 5.3.6p3, 5.4.0p2, 5.5.0b1.
Not reproduced with: 5.2.4f1.
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
- Polygons are created on the opposite side of the Sprite when the Sprite boundaries are above the edge of the Texture
- Render Graph Viewer Resource list becomes shrunk after using a filter that yields no results
- [Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices in "com.unity3d.player.UnityPlayerActivity/2D Colour Attachement"
- ResolveUsePasses now extracts passes from all subshaders including fallbacks, in contrast to documented behaviour
- [UIBuilder] Changes aren't detected on types implementing IList
Zorbaxy
Jun 13, 2017 14:05
What is a workaround for this? It is happening in 5.6.1p1 also, and saying it is "By Design" seems a bit strange on animated menus with those hiccups on first press on every button.
Salazar
May 01, 2017 10:27
Android build, unity 5.6.0 p3 same here.
tommyzat
Dec 12, 2016 18:44
This is reproducing for me even in 5.5.0p1