Search Issue Tracker
Fixed in 5.5.1
Votes
2
Found in
5.4.0p3
Issue ID
827110
Regression
Yes
[Android] Unaccounted time between:PlayerEndOffFrame and InputProcess which causes a huge performance issue on MotoG4
Steps to reproduce:
1) Download attached project 'MotoG4.zip' and open in Unity
2) Make sure 'Development Build' and Autoconnect Profiler' enabled
3) Build and run scene 'testy' on a device
4) Check performance in profiler
Expected result: section / activity should be covered by a profiler sample
Actual result : section / activity shows 'Unaccounted time between:PlayerEndOffFrame and InputProcess' which also causes a huge performance issue
Reproduced with: 5.4.3f1, 5.5.0f2, 5.6.0a3
Not reproduced with: 5.3.7p1
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
datacat
Dec 12, 2017 09:19
This problem still exist in 5.6.2p4 , and I use andriod phone MX4. It's very big problem!!
Guillaumzed
Mar 14, 2017 09:44
I still have 5200 InputProcess calls in the last 5.5.2p1update
I've opened this thread about it :
https://forum.unity3d.com/threads/loadscene-takes-way-too-long-to-charge-a-scene-on-android-5-5-2p1-inputprocess-issue.460958/
Perhaps a regression between 5.5.1 and 5.5.2 ?
RescuerRus
Nov 29, 2016 19:22
Huge fps drops in empty scene on android device. Confirmed that.