diff options
| author | Sanguk Jeon <uky.jeon@samsung.com> | 2020-09-02 19:15:00 +0900 |
|---|---|---|
| committer | Todd Kennedy <toddke@google.com> | 2020-09-17 20:09:23 -0700 |
| commit | 761e81f6a853cb0753a64ff3daf675793d5faa9c (patch) | |
| tree | 615ed98ed539bd7e271b72a5630f021f3426d5f1 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | 4e1e30e7bb66b8aa220651cfc186686993636736 (diff) | |
Ensure that binding state is false when handling dead binder
When a binding is disconnected, it is expected that binderDied() is
called after onBindingDied(). But, there exists a corner case where
the order is reversed. In this case, binderDied() cancels the
scheduling of MSG_UNBIND message, which blocks the chance of changing
mBinding value as false. As a results, mBinding value remains as true
even though the binding is disconnected. This would make the service
as unresponsive when a client tries reconnecting to the service.
This change ensures that mBinding becomes false even though binderDied()
is called before onBindingDied().
Bug: b/162753393
Test: compile & verify basic functions working
Change-Id: I66c5b130674a4355123fbac27f574d0d081e7b63
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions