tree 0416fae77553b50fbfd2373095eef2cd5e1a1405
parent 96129fb7bbde75f799a367f8eb60f137671cce53
author Jeff Chang <chengjeff@google.com> 1548329608 +0800
committer Jeff Chang <chengjeff@google.com> 1548329608 +0800

Fix a deadlock symptom between AM/WM

On the case,ProcessRecord.appNotResponding acquired the WMGlobalLock and waiting to
hold the AM service lock. Another thread hold the AM service lock and waiting to
acquire WMGlobalLock result in the issue.

Let the killAppCallback and serviceTimeoutCallback out of the WMGlobalLock scope.

Bug: 123173718
Test: atest ActivityStarterTests
Change-Id: I501309dc8fedbb226cd387ef6e6674a07a6d6ead