Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2017.4.17f1
Issue ID
1113139
Regression
No
[Android] AndroidJavaRunnable causes player to timeout/hang when quitting
Steps to reproduce:
1. Open attached project
2. Build & run on android device (development player)
3. Start profiling with Android Studio Profiler
4. In app click "Click me" button
5. in app click "Quit" button
6. See in profiler that it takes approx +10 seconds to stop running and timeout messages (see above) appear in logcat
7. Repeat but without clicking the "Click me" button and see that it stops running much quicker
Reproduced in: 2019.1.0a13, 2018.3.1f1, 2017.4.17f1, 2017.3.2f1
Fixed in: 2019.2.0a5, 2019.1.0b4, 2018.3.7f1, 2017.4.21f1
Tested device:
VLNQA00118, Google Pixel 2 XL (Pixel 2 XL), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00101, Samsung Galaxy Note8 (SM-N950U), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00138, Huawei P20 Pro (CLT-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, 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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2019.2):
Fixed in 2019.2a5 for new scripting runtime. Resolving as won't fix for the old Scripting Runtime (.NET 3.5). This was deprecated and removed in 2019.2.