diff options
| author | Robert Carr <racarr@google.com> | 2015-09-17 10:54:58 -0700 |
|---|---|---|
| committer | Rob Carr <racarr@google.com> | 2015-09-21 18:03:50 +0000 |
| commit | 64b5e1c4f9991cbd97050bd3f183bf510fce2077 (patch) | |
| tree | c54970912c9f3b53ae1d10a4c4c0141d5b60fa8e /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 7aa79efe80b790eef61ac355c0ce6c7b606e6f78 (diff) | |
Enforce a timeout for Content Providers to be published.
ActivityManagerService: In the case where we are launching
an application on behalf of a Content Provider request,
enforce a timeout inbetween the application attaching and
the content providers being published. Consider that a defective
content provider may block in ContentProvider::onCreate
indefinitely: in such a case the PROC_START_TIMEOUT has already
been removed as the activity manager must have called bindApplication.
In these cases, there will be nothing to wake threads blocking
on the (non timed) wait for provider to be published at the end of
ActivityManagerService::getContentProviderImpl. This can cause binder
threads to block 1 by 1 until eventually AMS runs out and becomes
unresponsive.
Bug: 22141958
Change-Id: I2226da5df5c79b37f0b896423b3c1eaa4a7ecbba
(cherry picked from commit da33c13434cb20a11b522374411a5b819503e4e0)
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions