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

Commit 78d15fd1 authored by hansson's avatar hansson Committed by android-build-merger
Browse files

Merge "fix misleading FATAL EXCEPTION IN SYSTEM PROCESS log"

am: c0c9f531

Change-Id: I25f1aad9e04c22e0cd4ffc848a53c30dd740bdac
parents 8fe8f5fa c0c9f531
Loading
Loading
Loading
Loading
+5 −4
Original line number Diff line number Diff line
@@ -71,10 +71,11 @@ public class RuntimeInit {
        public void uncaughtException(Thread t, Throwable e) {
            // Don't re-enter if KillApplicationHandler has already run
            if (mCrashing) return;
            if (mApplicationObject == null) {
                // The "FATAL EXCEPTION" string is still used on Android even though
                // apps can set a custom UncaughtExceptionHandler that renders uncaught
                // exceptions non-fatal.

            // mApplicationObject is null for non-zygote java programs (e.g. "am")
            // There are also apps running with the system UID. We don't want the
            // first clause in either of these two cases, only for system_server.
            if (mApplicationObject == null && (Process.SYSTEM_UID == Process.myUid())) {
                Clog_e(TAG, "*** FATAL EXCEPTION IN SYSTEM PROCESS: " + t.getName(), e);
            } else {
                StringBuilder message = new StringBuilder();