summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator.cpp
diff options
context:
space:
mode:
authorMartijn Coenen <maco@google.com>2020-06-17 14:42:13 +0200
committerMartijn Coenen <maco@google.com>2020-06-17 14:46:51 +0200
commitab0c7403d67f51fcc7f188cb5d34c2466e392211 (patch)
tree3ac3f11a1836b4bf6bb715b9824484134c948c44 /tools/aapt2/java/JavaClassGenerator.cpp
parent475cf18309d45303986e159a93f4f41818eede4b (diff)
Increase timeout waiting for ExternalStorageService to bind.
We've observed occasions where it can take a long time for the system_server main thread to come around to handling the bind of the service, for example because it's handling long-running jobs: 06-04 08:19:27.544 1000 1532 1532 W Looper : Slow dispatch took 2044ms main h=com.android.server.job.JobSchedulerService$JobHandler c=null m=1 Delays like this can cause us to fail binding to the external storage service for a user, and reset the whole storage stack, leading to unexpected results, especially if we timed out for trying to mount user 10, while user 0 has already been successfully mounted. Increase the timeout to 20 seconds; this gives us a lot more time to complete the bind. At the same time, we want to avoid risking holding the vold lock for too and/or any deadlocks. Add a WTF for when we do hit the timeout, to get a better grasp on how common this is. Bug: 158452122 Test: Boot device Change-Id: Ia8f6f121448f6b5e484fd3e8cca845fdd89afc23
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions