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

Unverified Commit bbd716a5 authored by Shai Barack's avatar Shai Barack Committed by Michael Bestas
Browse files

Remove explicit allowance for SystemUI in lock-free MessageQueue

This has been generating rare SysUI crashes in sync barrier removal.
Out of an abundance of caution, turn this off in SysUI.
We can re-enable in the new DeliQueue implementation when that's ready.

Fixes: 438822893
Flag: EXEMPT bugfix
Change-Id: I9aae321715692bf3ed3ecc84eca3301f096959f6
parent 61af5bd0
Loading
Loading
Loading
Loading
+0 −10
Original line number Diff line number Diff line
@@ -197,16 +197,6 @@ public final class MessageQueue {
            }
        }

        // Also explicitly allow SystemUI processes.
        // SystemUI doesn't run in a core UID, but we want to give it the performance boost,
        // and we know that it's safe to use the concurrent implementation in SystemUI.
        if (processName.equals("com.android.systemui")
                || processName.startsWith("com.android.systemui:")) {
            return true;
        }
        // On Android distributions where SystemUI has a different process name,
        // the above condition may need to be adjusted accordingly.

        // We can lift these restrictions in the future after we've made it possible for test
        // authors to test Looper and MessageQueue without resorting to reflection.
        return false;