Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2018.4.30f1
2021.2
Issue ID
1325636
Regression
No
[Android] Caching.ready takes significantly longer when opening the app for the first time after cache size has increased
Reproduction steps:
1. Download and open the submitted project "CachingTest.zip"
2. Build and run on Android
3. Press "Fill Cache" and wait for Assets to be downloaded
4. Close and kill the application
5. Open and use other applications to increase memory usage
6. Open the built project again and investigate the Caching.ready time
7. Close and kill the application
8. Open the built project again and investigate the Caching.ready time
Expected result: Caching.ready time is similar in steps 6 and 8
Actual result: Caching.ready time is significantly longer in step 6
Reproducible with: 2018.4.33f1, 2021.2.0a12
Reproduced on:
VLNQA00122, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: NOT FOUND, GPU: Mali-G72
VLNQA00331, Huawei P20 lite (ANE-LX1), Android 9, CPU: HiSilicon Kirin 659, GPU: Mali-T830 (step 6: ~48s, step 8: ~12s)
VLNQA00229, Oneplus OnePlus6T (ONEPLUS A6013), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630 (step 6: ~16s, step 8: ~4s)
VLNQA00012, Samsung Galaxy S6 (SM-G920F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760 (step 6: ~21s, step 8: ~11s)
VLNQA00334, Xiaomi Mi A3 (Mi A3), Android 11, CPU: Snapdragon 665 SM6125, GPU: Adreno (TM) 610 (step 6: ~27s, step 8: ~5s)
VLNQA00096, Samsung Galaxy S8 (SM-G950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71 (step 6: ~28s, step 8: ~15s)
Did not reproduce on:
iPad 9.7" 6th gen (14.4) (step 6 and step 8 and a few more tries all average to about 30-32s)
Notes:
Did not test on other streams as it takes multiple hours to test one version. Contact CQA if additional tests are required.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (2021.2.X):
Most of the time come from reading the disk to determine cache state. This can be very sensitive to how underlying storage works (caching in drivers etc.). If you launch game twice in quick succesion, disk is "warm" and reading is fast, if you perform some significant disk activity between the two launches, if will take much longer.