Closed Bug 1649494 Opened 7 months ago Closed 5 months ago

Crash in [@ mozilla::widget::AndroidAlerts::ShowPersistentNotification]


(GeckoView :: General, defect, P1)



(firefox-esr68 unaffected, firefox-esr78 unaffected, firefox79 wontfix, firefox80 wontfix, firefox81 verified, firefox82 verified)

82 Branch
Tracking Status
firefox-esr68 --- unaffected
firefox-esr78 --- unaffected
firefox79 --- wontfix
firefox80 --- wontfix
firefox81 --- verified
firefox82 --- verified


(Reporter: agi, Assigned: agi)




(Keywords: crash, Whiteboard: [geckoview:m82])

Crash Data


(1 file)

First report for this bug is 6/15, so either something we or AC did recently.

This bug is for crash report bp-140bf268-ae89-4d3b-b210-5eafa0200630.

Top 10 frames of crashing thread:

0 mozilla::widget::AndroidAlerts::ShowPersistentNotification widget/android/AndroidAlerts.cpp:86
1 nsAlertsService::ShowPersistentNotification toolkit/components/alerts/nsAlertsService.cpp:222
2 nsAlertsService::ShowAlertNotification toolkit/components/alerts/nsAlertsService.cpp:193
3 NS_InvokeByIndex xpcom/reflect/xptcall/md/unix/xptcinvoke_arm.cpp:167
4 XPCWrappedNative::CallMethod js/xpconnect/src/XPCWrappedNative.cpp:1140
5 XPC_WN_CallMethod js/xpconnect/src/XPCWrappedNativeJSOps.cpp:946
6 js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:576
7 Interpret js/src/vm/Interpreter.cpp:639
8 js::InternalCallOrConstruct js/src/vm/Interpreter.cpp:611
9 js::jit::DoCallFallback js/src/jit/BaselineIC.cpp:2992
Priority: -- → P2
Severity: -- → S3
Priority: P2 → P1
Whiteboard: [geckoview:m82]
Duplicate of this bug: 1658462
Assignee: nobody → agi

Agi and I chatted on Matrix about this, and we evaluated the option of explicitly specifying the extension URL at .We decided against that in favor of the above patch, because adding the moz-extension://UUID URL to the notification would cause "UUID" to appear in the notification, in the spot where the domain name would usually appear.

If we ever want to add the URL, we need to add a way to get the extension name (or somewhere similarly human-readable) to appear instead.

Pushed by
Don't assume a notification has a URL. r=aklotz
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → 82 Branch

Please nominate this for Beta approval when you get a chance.

Flags: needinfo?(agi)

Comment on attachment 9171958 [details]
Bug 1649494 - Don't assume a notification has a URL. a=RyanVM

Beta/Release Uplift Approval Request

  • User impact if declined: Crash when extensions create notifications (e.g. search by image).
  • Is this code covered by automated tests?: Yes
  • Has the fix been verified in Nightly?: Yes
  • Needs manual test from QE?: No
  • If yes, steps to reproduce:
  • List of other uplifts needed: None
  • Risk to taking this patch: Low
  • Why is the change risky/not risky? (and alternatives if risky): The fix is basically a null check.
  • String changes made/needed:
Flags: needinfo?(agi)
Attachment #9171958 - Flags: approval-mozilla-beta?

Comment on attachment 9171958 [details]
Bug 1649494 - Don't assume a notification has a URL. a=RyanVM

Approved for 81.0b4.

Attachment #9171958 - Flags: approval-mozilla-beta? → approval-mozilla-beta+

There's a conflict on mobile/android/geckoview/src/main/java/org/mozilla/geckoview/doc-files/ when trying to uplift this to beta.

Agi, could, you, please, take a look?

Flags: needinfo?(agi)
Attachment #9171958 - Attachment description: Bug 1649494 - Don't assume a notification has a URL. → Bug 1649494 - Don't assume a notification has a URL. a=RyanVM

This patch should now apply to Beta. I could swear I had access to push to beta directly but looks like I don't?

Flags: needinfo?(agi)

We can still reproduce this on Fenix Beta 81.1.0 with the steps from
Fixed on Nightly 9/2.

QA Contact: oana.horvath

The uplift in comment 11 didn't land in time for the 81.1.0 build.

FYI, the 81.1.0-beta.2 build should contain this fix.

Flags: needinfo?(oana.horvath)

Thanks Ryan, we have verified the fix on the 81.1.0-beta.2 build, no longer crashing.

Flags: needinfo?(oana.horvath)

It seems, as a result a new bug appeared:

You need to log in before you can comment on or make changes to this bug.