diff options
| author | Makoto Onuki <omakoto@google.com> | 2018-05-31 11:03:56 -0700 |
|---|---|---|
| committer | Makoto Onuki <omakoto@google.com> | 2018-05-31 14:52:51 -0700 |
| commit | b6c79ea065fc1adf383beabfacb401ff8b6466a8 (patch) | |
| tree | 04910cecc8b5ee6dd1b4730849a3c2ba8776dcbe /rs/java/android/renderscript/RenderScriptCacheDir.java | |
| parent | abed288a081c5016200b562ffdca75faac5574dc (diff) | |
Serialize AM.getContentProvider() calls in client side
Th wait() call in AMS.getContentProviderImpl() can cause a deadlock when it
starts a new process for a target provider and all system server binder threads
are reaching out to the same provider at the same time, because AMS won't be
able to receive a callback from the provider process.
Let's serialize access to AM.getContentProvider() to avoid this scenario.
Longer team, we should stop waiting in the system server and instead do so in
the client side.
Bug: 74523247
Test: Boot, add a google account, and let syncs run and finish.
Test: Watch free video on Coursera
Change-Id: If5be2dc4b6f22f72d1bb3aa1b5b4d49f20c8d94d
Diffstat (limited to 'rs/java/android/renderscript/RenderScriptCacheDir.java')
0 files changed, 0 insertions, 0 deletions