Closed Bug 1651221 Opened 4 years ago Closed 2 years ago

Crash in [@ android.app.RemoteServiceException: at android.app.ActivityThread$H.handleMessage(ActivityThread.java)]

Categories

(Fenix :: General, defect, P2)

Unspecified
Android

Tracking

(firefox95 wontfix, firefox96+ wontfix, firefox97+ wontfix, firefox99 wontfix, firefox100 wontfix, firefox101+ fixed, firefox102+ fixed, firefox103+ fixed)

RESOLVED FIXED
Tracking Status
firefox95 --- wontfix
firefox96 + wontfix
firefox97 + wontfix
firefox99 --- wontfix
firefox100 --- wontfix
firefox101 + fixed
firefox102 + fixed
firefox103 + fixed

People

(Reporter: bugzilla, Assigned: royang)

References

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-83f69f06-43ad-4fea-b7f6-372bf0200707.

Java stack trace:

android.app.RemoteServiceException
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1894)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:214)
	at android.app.ActivityThread.main(ActivityThread.java:7156)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:494)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:975)
Flags: needinfo?(kbrosnan)
Depends on: 1697255

Crash volume is still very high in 95.

Severity: -- → S1
OS: Unspecified → Android
Priority: -- → P1

Given the discussion in the upstream ticket, it sounds like we should downgrade the priority & severity here.

Severity: S1 → S2
Priority: P3 → --

#1 top crash for both Fenix and Focus 101. Seems to have spiked considerably recently.

The regressing change (https://github.com/mozilla-mobile/android-components/pull/11991) has been backed out from 101+ and it appears that the crash rate for 101.2.0 with that backout is back to where it was before.

Assignee: nobody → royang
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
See Also: → 1774678
Component: Stability → General
You need to log in before you can comment on or make changes to this bug.