Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit c661b660 authored by Zimuzo's avatar Zimuzo
Browse files

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
parent 9e03e1d2

init/service.cpp

+1 −1
Original line number Diff line number Diff line
@@ -406,7 +406,7 @@ void Service::Reap(const siginfo_t& siginfo) { 


    // If we crash > 4 times in 4 minutes, reboot into bootloader or set crashing property

    boot_clock::time_point now = boot_clock::now();

    if (((flags_ & SVC_CRITICAL) || classnames_.count("updatable")) && !(flags_ & SVC_RESTART)) {

    if (((flags_ & SVC_CRITICAL) || !pre_apexd_) && !(flags_ & SVC_RESTART)) {

        if (now < time_crashed_ + 4min) {

            if (++crash_count_ > 4) {

                if (flags_ & SVC_CRITICAL) {