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)
Tracking
(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)
Updated•4 years ago
|
Flags: needinfo?(kbrosnan)
Updated•3 years ago
|
Comment 1•2 years ago
|
||
Crash volume is still very high in 95.
Severity: -- → S1
status-firefox95:
--- → affected
status-firefox96:
--- → affected
status-firefox97:
--- → ?
tracking-firefox96:
--- → ?
tracking-firefox97:
--- → ?
OS: Unspecified → Android
Priority: -- → P1
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Given the discussion in the upstream ticket, it sounds like we should downgrade the priority & severity here.
Severity: S1 → S2
Priority: P3 → --
Updated•2 years ago
|
status-firefox100:
--- → affected
status-firefox101:
--- → affected
status-firefox99:
--- → wontfix
Priority: -- → P2
Comment 3•2 years ago
|
||
#1 top crash for both Fenix and Focus 101. Seems to have spiked considerably recently.
Updated•2 years ago
|
tracking-firefox102:
--- → +
Comment 4•2 years ago
|
||
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
tracking-firefox103:
--- → +
Resolution: --- → FIXED
Updated•2 years ago
|
Component: Stability → General
You need to log in
before you can comment on or make changes to this bug.
Description
•