| commit | c661b660fe1eaa82e13ca898390517a94df256c8 | [log] [tgz] |
|---|---|---|
| author | Zimuzo <zezeozue@google.com> | Mon Jan 14 16:16:07 2019 +0000 |
| committer | Zimuzo <zezeozue@google.com> | Mon Jan 14 16:22:10 2019 +0000 |
| tree | 70c6f5b57adbc66b7766a58b97b8a9a329ed5b5c | |
| parent | 9e03e1d2dc3995da90f749a6fbcb73e66f7d4ced [diff] |
Identify post-apexd crashing processes I7d47ea1223f7792a834981c729694242ab3f28c9 tried to identify processes that crash after apexd is ready by introducing an 'updatable' class. However, after I7ca67755dc0656c0f0c834ba94bf23ba9b1aca68 we now have a pre_apexd_ field we can reuse instead of introducing a new class type. Bug: 120598832 Test: Killing a !pre_apexd_ process 4 times in 4mins sets the ro.init.updatable.crashing prop while killing a pre_apexd_ process reboots into the bootloader Change-Id: Icb9f405b9b54d11546bbf6d3bc28212936a78b0e