Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2017.4.X, 2018.4.X, 2019.2.X, 2019.3.X
Votes
66
Found in
2017.4
2018.4
2018.4.9f1
2019.1
2019.2
2019.3
2020.1
Issue ID
1186295
Regression
No
[Android] 64 bit Build with Physics.Processing runs at a very low FPS
Steps to reproduce:
1. Open user's attached project "PerformanceDrop.zip"
2. Build it on Huawei Huawei mate 20 pro
3. Run it and tap on the screen
4. Notice a massive FPS drop to about 3 FPS
Expected results: The app is running at 30 Frames
Actual results: The app starts running at 13 Frames and drops to about 3 frames after interaction
Reproducible with: 2017.4.33f1, 2018.4.9f1, 2019.1.14f1, 2019.2.7f1, 2019.3.0b4, 2020.1.0a5
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
Samsung Galaxy Note10 (SM-N970U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Not Reproducible with:
VLNQA00166, Huawei P20 (EML-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, GPU: Mali-G72
VLNQA00136, Samsung Galaxy S9+ (SM-G965F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00277, Asus ROG Phone (ASUS_Z01QD), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00165, Samsung Galaxy S7 (SM-G930F), Android 7.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
VLNQA00216, Razer Phone 2 (Phone 2), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00121, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00027, Xiaomi MI MAX (MI MAX), Android 7.0, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00017, Huawei Nexus 6P (Nexus 6P), Android 8.0.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00287, Motorola moto g(7) power (moto g(7) power), Android 9, CPU: Snapdragon 625 MSM8953, GPU: Adreno (TM) 506
Massive FPS drops on some 64bit Android devices
Comments (26)
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
ferdibakirezer
Nov 06, 2019 08:11
Exact same issue here! blocked by this...
ferdielite
Nov 06, 2019 08:05
having the same issue
mohawk_
Nov 05, 2019 12:58
me too
experiencing the same issue
Actualizator
Nov 05, 2019 12:36
Same problem here.
OlegPavlov
Nov 05, 2019 12:33
The same problem and no workaround
Kuptsevych-Yuriy
Nov 05, 2019 12:20
same problem
a-dolbilov
Nov 05, 2019 11:36
Have the same problem for Xiaomi Black Shark 2 (Snapdragon 855), Xiaomi Mi 9 (Snapdragon 855), Samsung Galaxy S9 (Exynos 9810)...
Have experienced this problem under Unity 2018.3.13f1, Unity 2018.4.12f1, 2019.2.11f1
unity_NCIi9Mrnhehs8Q
Nov 05, 2019 11:08
I'm having the same problem.
teslatron
Nov 05, 2019 10:03
Experiencing the same issue on Huawei mate 20 pro & Huawei p30 pro
unity_ox-qxw7nnvdW5A
Nov 05, 2019 07:31
I'm having the same problem. We're experiencing a physical degradation caused by Unity on some mobile devices, and we're getting stuck now because Google requires 64bit support.