wolvic-chromium crashes on startup after M123 chromium update. The issue only happens in release builds and can be fixed by reverting https://chromium-review.googlesource.com/c/chromium/src/+/4361339, we need to figure out why this optimization is causing the crashes.
Java stack trace:
java.lang.AssertionError: Must only be used on a single thread.
at org.chromium.base.ThreadUtils$ThreadChecker.assertOnValidThread(ThreadUtils.java:65)
at org.chromium.base.ObserverList.addObserver(ObserverList.java:72)
at org.chromium.base.ApplicationStatus.registerApplicationStateListener(ApplicationStatus.java:724)
at org.chromium.base.ApplicationStatus$3.run(ApplicationStatus.java:796)
at org.chromium.base.task.PostTask.runOrPostTask(PostTask.java:114)
at org.chromium.base.ThreadUtils.runOnUiThread(ThreadUtils.java:191)
at org.chromium.base.ApplicationStatus.registerThreadSafeNativeApplicationStateListener(ApplicationStatus.java:782)
at android.os.MessageQueue.nativePollOnce(Native Method)
at android.os.MessageQueue.next(MessageQueue.java:335)
at android.os.Looper.loopOnce(Looper.java:167)
at android.os.Looper.loop(Looper.java:304)
at android.app.ActivityThread.main(ActivityThread.java:7918)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1010)
wolvic-chromium crashes on startup after M123 chromium update. The issue only happens in release builds and can be fixed by reverting https://chromium-review.googlesource.com/c/chromium/src/+/4361339, we need to figure out why this optimization is causing the crashes.
Java stack trace:
Native stack trace: