1805973 - about:crashparent doesn't display the crash system notification on Android 9 Xiaomi device

Status: NEW

(Fenix :: Crash Reporting, defect, P3)

Description

[Chris Peterson [:cpeterson]]

From github: https://github.com/mozilla-mobile/fenix/issues/26382.

Steps to reproduce

1. Open a few tabs on Fenix.
2. Tap the URL bar and access about:crashparent.
3. Observe the android notification bar.

Expected behaviour

As per https://github.com/mozilla-mobile/fenix/issues/26080, when about:crashparent is entered in the URL bar, the browser closes and the crash system notification is displayed.

Actual behaviour

When about:crashparent is entered in the URL bar, the browser closes, and no crash notification appears in the system notification bar. After going about:crashparent a second time, the "Sorry" dialog box is displayed.

Device name

Xiaomi Redmi Note 8T

Android version

Android 9

Firefox release type

Firefox Nightly

Firefox version

Latest Nightly 105 from 08/08

Device logs

No response

Additional information

https://user-images.githubusercontent.com/89388888/183621355-31d9f370-d435-47c4-adad-9e01a6aace97.mp4

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

Comment 1

[Makoto Kato [:m_kato]]

I can reproduce this on another my Xiaomi deivce (Xiaomi Redmi 9T / Android 11 / MIUI 12.5.12). Although attaching logcat, there is no log for CrashReporter.

12-20 13:06:21.200 21902 21945 W google-breakpad: ExceptionHandler::GenerateDump cloned child 
12-20 13:06:21.200 21902 21945 W google-breakpad: 22357
12-20 13:06:21.200 21902 21945 W google-breakpad: 
12-20 13:06:21.200 21902 21945 W google-breakpad: ExceptionHandler::SendContinueSignalToChild sent continue signal to child
12-20 13:06:21.201 22357 21945 W google-breakpad: ExceptionHandler::WaitForContinueSignal waiting for continue signal...
...
12-20 13:06:22.222 21902 21902 I GeckoSession: handleMessage GeckoView:PageStart uri=
...
12-20 13:06:22.359 22226 22254 I Gecko   : Exiting due to channel error.
12-20 13:06:22.360 22005 22157 I Gecko   : Exiting due to channel error.
12-20 13:06:22.367  1533  2217 W InputDispatcher: channel '4434c5e org.mozilla.fenix/org.mozilla.fenix.App (server)' ~ Consumer closed input channel or an error occurred.  events=0x9
12-20 13:06:22.367  1533  2217 E InputDispatcher: channel '4434c5e org.mozilla.fenix/org.mozilla.fenix.App (server)' ~ Channel is unrecoverably broken and will be disposed!
12-20 13:06:22.370  1533  2533 I ActivityManager: Process org.mozilla.fenix (pid 21902) has died: fg  TOP 
12-20 13:06:22.370  1533  1731 I Process : PerfMonitor : current process killing process group. PID: 21902
12-20 13:06:22.371  1533  5511 I WindowManager: WIN DEATH: Window{4434c5e mode=0 rootTaskId=1391 u0 org.mozilla.fenix/org.mozilla.fenix.App}
12-20 13:06:22.377  1533  5511 W InputDispatcher: Attempted to unregister already unregistered input channel '4434c5e org.mozilla.fenix/org.mozilla.fenix.App (server)'
...

Comment 2

[Makoto Kato [:m_kato]]

When debugging this, crash service won't be started by /system/bin/am. I found interesting comment in https://stackoverflow.com/questions/54275678/how-to-start-service-from-ndk-android. Xiaomi device doesn't allow to start service by am command?

Comment 3

[Zac McKenney [:zmckenney]]

unrelated to 1808616 so removing the connection. This seems connected to 1805974 so I've added that connection.