1857157 - [Bug]: about:crashcontent/about:crashparent not working on different devices

Status: NEW

(Firefox for Android :: Crash Reporting, defect, P3)

Description

[Delia Pop (Android QA)]

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

Steps to reproduce

1. Open several tabs in Fenix.
2. Insert about:crashparent in the URL field to trigger a crash in app.
3. Observe if the app crashes.

Expected behaviour

After entering about:crashparent in the url bar, the app crashes and closes. A dialog is displayed.

Actual behaviour

After entering about:crashparent in the url bar, the application remains unresponsive.

Device name

Tab Huawei MediaPad M2, Xiaomi mi4i

Android version

(Android 5.1.1), Android 5.0.2

Firefox release type

Firefox Beta

Firefox version

Initially reported on 97.0.0-beta.1 , still reproducible in the latest Firefox for Android versions Nightly 120.0a1, Beta 119.0b5 and RC 118.1.1 .

Device logs

Provided logs below from Xiaomi mi4i (Android 5.0.2)

Additional information

https://user-images.githubusercontent.com/89388888/149524736-f0ddc1df-b039-429b-aa6c-930386b3401a.mp4

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

Comment 1

[Delia Pop (Android QA)]

Attachment: Screenshot_2023-10-05-10-34-34.png

Still reproducible on Beta 119.0b5 with Tab Huawei MediaPad M2 (Android 5.1.1), as well on latest Nightly 120.0a1 and RC 118.1.1 versions.
After inserting about:crashparent in the URL field to trigger a crash in app, the application remains unresponsive and has to be closed/restarted.
Please note the tab crash reported, about:crashcontent, works as expected.

Comment 2

[Arturo Mejia [:amejia]]

Hi Delia 👋,
Thanks filing this, would you mind to capture some logs ?
Is this is something that is blocking the QA team?

Thanks in advance!

Comment 3

[Gabriele Svelto [:gsvelto]]

If I'm reading this correctly the report comes from a very old version of Fenix (97). It should be re-tested with the current nightly before we confirm it. Both about:crashcontent and about:crashparent work fine on my Android devices using the current nightly and release builds.

Comment 4

[Delia Pop (Android QA)]

Attachment: logcat (2).txt

Hi Arturo, here are the logs from Xiaomi mi4i (Android 5.0.2), another device on which the application remains unresponsive after entering about:crashparent in the url bar.
Unfortunately I cannot provide logs from the second device, Huawei MediaPad M2 (Android 5.1.1), due to connectivity issues and no logs are generated in about:crashes either.

To sum up, the unresponsive state is only reproducible for about:crashparent (about:crashcontent works as expected) with:

• Huawei MediaPad M2 (Android 5.1.1)
• Xiaomi mi4i (Android 5.0.2)

The issue is not reproducible with high end devices or the following devices:

• Samsung Galaxy Tab (Android 6)
• OnePlus A3000 (Android 6)
• Sony Xperia Tab (Android 6.1)

Regarding your question, testing on these low end devices (Android 5 is our lowers version available) is very time consuming, hindered in general by numerous issues only reproducible on these devices and by the bad performance.
But strictly referring to this particular issue, I would say that it does not block us, except during build validation when we run a test case which verifies that the tab crasher and the app crasher work (in this case we have to fail the test with this known issue). Apart from that, if a general crash is encounter on these devices, the application remains responsive and log crashes are available.
I hope this helps.

Comment 5

[Delia Pop (Android QA)]

Attachment: aboutcrashparent.mp4

Adding a video recording of the issue from the latest Nightly 120.0a1 from 10/06 on Huawei MediaPad M2 (Android 5.1.1).

Comment 6

[Denis Müller [:Webworkr]]

133.0a1 (Build #2016048607), hg-c72250bf66d5+
GV: 133.0a1-20241006093023
AS: 133.20241005050312

Samsung Galaxy A13 5G (SM-A136B)
https://doc.samsungmobile.com/SM-A136B/EUX/doc.html

about:crashcontent: The "close" button properly closes the tab. "Restore tab" leads to the reload of the "crashcontent" tab. This is misleading. However, this is probably due to the fact that a crash is deliberately caused here and no previous tab content is available that could be restored.

about:crashparent causes the app to crash immediately.

In all cases, the crash is logged under "Settings" > "About ..." > "Crashes" is logged. I cannot check whether a transfer to an external device takes place.