801617 - android.app.RemoteServiceException: at android.app.ActivityThread$H.handleMessage(ActivityThread.java)

Status: RESOLVED INCOMPLETE

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

Description

[Scoobidiver (away)]

There are 54 crashes across all versions, including bp-6c88d22a-a768-4537-a001-5ffc92121015.

android.app.RemoteServiceException: Bad notification posted from package org.mozilla.fennec: Couldn't expand RemoteViews for: StatusBarNotification(pkg=org.mozilla.fennec id=1135163465 tag=null score=0 notn=Notification(pri=0 contentView=org.mozilla.fennec/0x1090071 vibrate=null sound=null defaults=0x0 flags=0x0 kind=[null]))
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1374)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loop(Looper.java:137)
	at android.app.ActivityThread.main(ActivityThread.java:4931)
	at java.lang.reflect.Method.invokeNative(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:511)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
	at dalvik.system.NativeStart.main(Native Method)

More reports at:
https://crash-stats.mozilla.com/report/list?signature=android.app.RemoteServiceException%3A+at+android.app.ActivityThread%24H.handleMessage%28ActivityThread.java%29

Comment 1

[Marcia Knous [:marcia]]

This crash is #5 overall in the latest 65.0.1 release. Updating flags.

Comment 2

[Liz Henry (:lizzard) (relman/hg->git project)]

This is a very high volume crash in 65 and likely will be in 66 but I don't think we'll have a fix for 66 release. If we do land something for 68/67, we could consider uplift for a later dot release so let me know if that happens.

Comment 3

[Marcia Knous [:marcia]]

Top crash device is Blackberry STH100-2, followed by ONEPLUS A5010 and ONEPLUS A5000. Comments are not particularly useful and no particular trend in URLs.

(26.37% in signature vs 10.61% overall) useragent_locale = en-US ∧ "WebGL?" in app_notes = true
(21.59% in signature vs 06.56% overall) android_version = 26 (REL) ∧ "WebGL?" in app_notes = true
(21.59% in signature vs 06.56% overall) "WebGL+" in app_notes = true ∧ android_version = 26 (REL)

Comment 4

[Stefan Deiac]

Hi, I tried to reproduce this crash using OnePlus 5T (Android 9) and Samsung Galaxy S8 (Android 9) on the latest version of Nightly 68.0a1 (2019-03-19).
The scenarios tested:

• Watch a video in full screen;
• Watch a video in private window;
• removing history links;
• follow links from CNN;

Due to the fact that this ticket is a critical one, can we do something from the QA side to help with the investigation?

Comment 5

[Marcia Knous [:marcia]]

Discussed during Fennec triage today. Although 65.0.1 has over 21576 crashes, it is too early in 66 to tell what the crash volume will be. Also I am removing the second crash signature since it hasn't shown any crashes in the last 6 months. Current comments are no useful.

Comment 6

[Pascal Chevrel:pascalc (PTO until Sept 2)]

No crashes on 67 beta, either this got fixed or the signature changed.

Comment 7

[Marcia Knous [:marcia]]

Liz: Should we untrack this for 66 so it doesn't come up in the Fennec blocking query? Currently the signature is not seen in 67 or 68.

Comment 8

[Liz Henry (:lizzard) (relman/hg->git project)]

Too late for a fix in 66 at this point.

Comment 9

[Marcia Knous [:marcia]]

#5 top crash currently in 68 beta. This crash doesn't seem to have affect 67 at all.

Comment 10

[Brad Arant]

This error is usually caused by using a UX component on a status bar or notification message that cannot be used on those objects. I was attempting to verify but cannot recreate.

Comment 11

[Marcia Knous [:marcia]]

This is the #4 top overall crash in Fennec release.

Comment 12

[Marcia Knous [:marcia]]

Several of the comments mention Twitter:

• Firefox was unresponsive when browsing twitter. Even after closing it, it was still unresponsive until it crashed.
• It crashed after I opened the twitter app from firefox

Almost 6500 crashes on 68 release.

Comment 13

[Marcia Knous [:marcia]]

High volume Fennec 68 crash with almost 24K crashes.

Comment 14

[Marcia Knous [:marcia]]

Moving this up to a P1 since it is now in the top crash realm.

Comment 15

[Chris Peterson [:cpeterson]]

Downgrading from priority P1 to P2.

Comment 16

[BMO Automation]

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.