Closed Bug 1522107 Opened 7 years ago Closed 5 years ago

(Fennec) The Crash Reporter has lost its touch

Categories

(Firefox for Android Graveyard :: General, defect, P3)

Product:
Firefox for Android Graveyard
Component:
General
Version:
Firefox 66
Platform:
x86
Android
Type:
defect

Tracking

(firefox66 affected, firefox67 unaffected, firefox68 affected)

Status:
RESOLVED INCOMPLETE
Tracking Flags:
Tracking Status
firefox66 --- affected
firefox67 --- unaffected
firefox68 --- affected

People

(Reporter: csheany, Unassigned)

Details

User Agent: Mozilla/5.0 (Android 7.1.1; Tablet; rv:66.0) Gecko/66.0 Firefox/66.0

Steps to reproduce:

  1. Crash the browser

Actual results:

Nothing happens.

Expected results:

The pop up should appear.

Marcia, would you mind taking a look?

Flags: needinfo?(mozillamarcia.knous)

Hello Csheany, I tried to reproduce this issue with the following steps:

  • Launch Fennec and open any tab
  • Open another tab
  • Tap on the URL bar and type about:crashparent

Note that after crashing fennec, a crash report was displayed.(I did this for more than 10 times)
I used a Google Pixel 3 XL with Android P.
Can you please mention how exactly are you crashing fennec and what device/android version are you using?

Flags: needinfo?(csheany)

(In reply to csheany from comment #1)

Marcia, would you mind taking a look?

I was able to crash my Pixel 3 successfully using the latest nightly. That device is running Android Pie.

Flags: needinfo?(mozillamarcia.knous)

Thank you both for your response.

It does respond properly with that method.

See Bug 1510340

Flags: needinfo?(csheany)

Your HLS video play back is a OOM. The device is going to be in a bad state. We won't be able to capture every crash when the device is in near OOM conditions.

I understand that.

This has been happening for a couple days.

I used to be able to capture a few in a row but now I don't seem to be capturing any.

Even Bug 1511566 which is even worse.

Have there been any changes to the Crash Reporter?

Flags: needinfo?(cpeterson)

(In reply to csheany from comment #7)

Have there been any changes to the Crash Reporter?

There is a known bug with the GeckoView 65 crash reporter in Focus 8.0, but I don't know of any recent changes to the crash reporter in Fennec 66.

We appear to still be receiving crash reports from Fennec 66 Beta users:

https://crash-stats.mozilla.com/search/?product=FennecAndroid&version=66.0b&date=%3E%3D2018-09-08T16%3A56%3A00.000Z&date=%3C2019-03-08T16%3A56%3A00.000Z&_facets=signature&_facets=version&_sort=-date&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-version

Flags: needinfo?(cpeterson)

about:crashparent shows the Fennec crash reporter as expected for me in Fennec 65, 66.0b11, 66.0b13, and 67.0a1 on my Moto G5 Plus running Android 8.1.

I just tested both Nightly 67 and beta 66 and was able to successfully generate a crash on both.

Thank you for your response.

Are they different?

If it existed in 65 is there reason to believe it wouldn't anymore?

What was the cause?

Has the GeckoView Crash Reporter been fixed?

Do you have any Android Developer Options enabled, such as "Don't Keep Activities", that might cause background apps to get killed sooner than they usually might? Perhaps that is causing the crash reporter from launching after Fennec crashes?

That Developer Option is not enabled and "Limit Background Activities" is standard.

csheany, is this still the case for you?

status-firefox66: --- → affected
status-firefox67: --- → ?
Flags: needinfo?(csheany)

Unfortunately

Flags: needinfo?(csheany)

Hmm. What is the specific hardware again?

Samsung Galaxy Tab A

Model SM-T350

csheany is able to submit some crashes such as bug 1544888.

As I said in comment 5 the crash reporter may fail to report crashes when the system is in a near OOM state. The device does not have any resources to process the crash thus the crash reporter fails to work.

To clarify, that was with Reference Browser on a different device.

Summary: The Crash Reporter isn't working on Android → (Fennec) The Crash Reporter has lost its touch

So far it looks as if no one has been able to reproduce this on any devices outside the one referenced in Comment 18. We also don't seem to have other reports of the crash reporter not working with the exception of those people running Android Q which is a known issue. Marking this as P3 for now.

Priority: -- → P3

(In reply to Marcia Knous [:marcia - needinfo? me] from comment #21)

So far it looks as if no one has been able to reproduce this on any devices outside the one referenced in Comment 18. We also don't seem to have other reports of the crash reporter not working with the exception of those people running Android Q which is a known issue. Marking this as P3 for now.

I have been having problems with the crash reporter on my Android P/Android 9 phone. While trying to reproduce bug 1543262 on my Pixel 3, 9/10 crashes I've triggered with Firefox 68 beta have crashed to the home screen instead of the crash reporter.

I've only seen the defective crash reporter behavior with Firefox 68 beta so far. When I was reproducing the same bug with Firefox 66 release (specifically 66.0.2), 100% of the crashes I triggered got the crash reporter.

Flags: needinfo?(mozillamarcia.knous)

(In reply to J Nonamano from comment #22)

I have been having problems with the crash reporter on my Android P/Android 9 phone. While trying to reproduce bug 1543262 on my Pixel 3, 9/10 crashes I've triggered with Firefox 68 beta have crashed to the home screen instead of the crash reporter.

I've only seen the defective crash reporter behavior with Firefox 68 beta so far. When I was reproducing the same bug with Firefox 66 release (specifically 66.0.2), 100% of the crashes I triggered got the crash reporter.

Correction: I meant Firefox 67 beta.

Adding Sorina - Have you seen issues with crash reporter not firing during your testing on Android Pie? Thanks.

Flags: needinfo?(mozillamarcia.knous) → needinfo?(sorina.florean)

Hello

I have managed to reproduce the issue on a Samsung Galaxy Tab A 2016 (Android 7.0) using the method found in bug 1511566 which according to Comment 5 is to be expected, however on a newer device, a Samsung Galaxy S8+ (Android 8.0) the crash is recorded consistently on all available versions: Release 66.0.5, Beta 67.0b18 and Nightly 68.0a1 (2019-05-14).
I have found nothing to indicate that the crash reported has lost it's effectiveness.

(In reply to Marcia Knous [:marcia - needinfo? me] from comment #24)

Adding Sorina - Have you seen issues with crash reporter not firing during your testing on Android Pie? Thanks.

I wasn't able to reproduce on Android Pie devices, but I managed on Xiaomi Mi Pad 2(Android 5.1) - latest Nightly build and Beta following the steps from comment 2. Unfortunately, we can't get any longs from the device.

The crash reporter is working as expected on Fenix, the same device.

Flags: needinfo?(sorina.florean)
Status: UNCONFIRMED → NEW
status-firefox67: ? → unaffected
status-firefox68: --- → affected
Ever confirmed: true
OS: Unspecified → Android
Hardware: Unspecified → x86

Hi!
I can reproduce this on RC 68.0, Beta 68.0b14, Nightly 68.0a1 (2019-06-28) with OnePlus 5T (Android 9) following the steps:

Precondition: Have "Don't restore after quitting Nightly" set in Restore Tabs.

  1. Visit 2, 3 pages in different tabs and go to about:crashparent;
  2. From the Firefox crash report choose "Restart Nightly";
  3. Observe the restored tabs.

Expected result:
The tabs opened at step 1 are restored.

Actual result:
Firefox crash report is displayed again.

Notes:

  • After this behavior if you exit Fennec from Task Manager or from android settings, the tabs are restored at the first attempt.

I created Bug 1562831 for the issue described in Comment 27.

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.