diff options
| author | 2022-10-03 22:05:29 +0800 | |
|---|---|---|
| committer | 2022-10-13 06:54:28 +0000 | |
| commit | d060ed56975495a8f6bff86f8b41f4d0a08457ea (patch) | |
| tree | f3cea6f69e278d379172ced5ba6d2e519763b634 /libs/androidfw/ResourceTimer.cpp | |
| parent | d08eb3f984d9183279aa39cf9e04cfa3a3e23a68 (diff) | |
Dump App exit reason if the remote service died.
We received many bugs the ContentCaptureService entered zombie
state but we don't know the reason why the process died. The issue
timing didn't be captured in bugreport.
Currently, the AbstractRemoteService will enter an odd state if the
service cannot be reconnected. This state does not allow the requests
be sent until the service be reconnected again on an unknown timing.
In some cases, it is expected the service will not be reconnected.
e.g. app stop from settings. We should fix the problem in the
AbstractRemoteService but before doing this, we try to add debugging
signal in bugreport to help us understand if the existing issues come
from this odd state for reasonable reasons.
Bug: 248218072
Bug: 250859760
Test: disable app and dumpsys content_capture
Change-Id: Ia33462006a3925754001562b0d80540b9b0bc45d
Diffstat (limited to 'libs/androidfw/ResourceTimer.cpp')
0 files changed, 0 insertions, 0 deletions