Closed Bug 1802619 Opened 2 years ago Closed 2 years ago

Crash in [@ java.lang.NullPointerException: at org.mozilla.fenix.settings.deletebrowsingdata.DeleteBrowsingDataFragment$$ExternalSyntheticLambda2.onClick(R8$$SyntheticClass:20)]

Categories

(Fenix :: History, defect, P1)

Unspecified
Android
defect

Tracking

(firefox107 wontfix, firefox108 wontfix, firefox109 wontfix, firefox110 verified, firefox111 verified)

VERIFIED FIXED
111 Branch
Tracking Status
firefox107 --- wontfix
firefox108 --- wontfix
firefox109 --- wontfix
firefox110 --- verified
firefox111 --- verified

People

(Reporter: cpeterson, Assigned: vdreghici)

References

Details

(Keywords: crash, topcrash, Whiteboard: [fxdroid])

Crash Data

Attachments

(3 files)

Crash report: https://crash-stats.mozilla.org/report/index/119847c2-5663-432e-90e5-004ec0221118

Java stack trace:

java.lang.NullPointerException
	at org.mozilla.fenix.settings.deletebrowsingdata.DeleteBrowsingDataFragment$$ExternalSyntheticLambda2.onClick(R8$$SyntheticClass:20)
	at androidx.appcompat.app.AlertController$ButtonHandler.handleMessage(AlertController.java:38)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loopOnce(Looper.java:226)
	at android.os.Looper.loop(Looper.java:313)
	at android.app.ActivityThread.main(ActivityThread.java:8663)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:567)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)

This crash looks like a regression in 107.0a1 on or before 2022-10-02.

Severity: -- → S2

The bug is linked to a topcrash signature, which matches the following criterion:

  • Top 10 AArch64 and ARM crashes on beta

For more information, please visit auto_nag documentation.

Keywords: topcrash
Component: General → History
Priority: -- → P2
Whiteboard: [fxdroid]

Video reproducing the crash

The steps for reproducing the crash are the following:

  • Go to settings.
  • Go to delete browsing data.
  • Select any options BUT include the "Open tabs" option, since it is the only one taking the user to the settings page after deletions is done.
  • Tap Delete browsing data.
  • Tap Delete.
  • While the process of deletion is in progress, the user is still able to tap "Delete browsing data again", leading to displaying the confirmation dialog again.
  • If the process is finished and user is taken back, if the confirmation dialog is still displayed and Delete button is pressed after user was taken back to settings, the app will crash.
    (Check video attached)

Expected behavior:

  • When the deletion is in progress, the user should not be able to tap again the "Delete browsing data" and open the dialog.
Assignee: nobody → Vlad.DreghiciPopa
Rank: 111
Priority: P2 → P1
Status: NEW → RESOLVED
Closed: 2 years ago
Flags: qe-verify+
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch

Verified as fixed on the latest Nightly 111.0a1 (2023-01-31) build.
Devices used:

  • Xiaomi Mi11 Lite (Android 11).
  • Oppo Find X5 (Android 12).
  • Google Pixel 7 (Android 13).

Marking the ticket as verified.

Status: RESOLVED → VERIFIED
Flags: qe-verify+

Do we want to uplift that patch in our last beta or is it OK to let it ride the 111 train and potentially uplift the patch for the 110 planned dot release?

Flags: needinfo?(cpeterson)

(In reply to Pascal Chevrel:pascalc from comment #7)

Do we want to uplift that patch in our last beta or is it OK to let it ride the 111 train and potentially uplift the patch for the 110 planned dot release?

I think we should uplift the fix to beta. The fix looks pretty safe. It only affects code paths related to the settings for deleting browsing history, so even if the fix introduces a new bug, the impact would be small.

Flags: needinfo?(cpeterson) → needinfo?(pascalc)

Verified as fixed on the latest Beta 110.0b6 build using the steps above.
The "Delete browsing data" button cannot be tapped while the process of deletion is in progress.
Device used: Google Pixel 7 (Android 13).
Marking as verified for 110.

Flags: qe-verify+
See Also: → 1827650
See Also: → 1851259
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: