Crash in [@ android.app.RemoteServiceException: at android.app.ActivityThread$H.handleMessage] org.mozilla.fenix.media.MediaSessionService
Categories
(Firefox for Android :: General, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox101 | --- | wontfix |
| firefox102 | --- | wontfix |
| firefox103 | --- | wontfix |
| firefox104 | --- | wontfix |
| firefox106 | --- | wontfix |
| firefox107 | --- | wontfix |
| firefox108 | --- | wontfix |
| firefox109 | --- | affected |
| firefox110 | --- | affected |
| firefox111 | --- | affected |
| firefox112 | --- | affected |
| firefox116 | --- | affected |
| firefox117 | --- | affected |
| firefox118 | --- | affected |
People
(Reporter: cpeterson, Unassigned)
References
Details
(Keywords: crash)
Crash Data
This is a generic crash signature, but nearly all of the crash reports' Java Stack Trace (Raw) fields mention the same org.mozilla.firefox/org.mozilla.fenix.media.MediaSessionService service.
Crash report: https://crash-stats.mozilla.org/report/index/59e8d1bb-2f34-4efb-ad21-72bf00220616
Java stack trace:
android.app.RemoteServiceException: Context.startForegroundService() did not then call Service.startForeground(): ServiceRecord{21d92e6 u0 org.mozilla.firefox/org.mozilla.fenix.media.MediaSessionService}
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2258)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:246)
at android.app.ActivityThread.main(ActivityThread.java:8633)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:602)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1130)
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Comment 1•3 years ago
|
||
Bug 1651221 fixed a recent spike in org.mozilla.fenix.media.MediaSessionService exceptions: https://github.com/mozilla-mobile/fenix/issues/17714
RyanVM said in bug 1651221 comment 4:
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.
We can use this bug to track the exceptions before the bug 1651221 regression.
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Updated•3 years ago
|
Comment 2•3 years ago
|
||
The bug is linked to a topcrash signature, which matches the following criteria:
- Top 10 AArch64 and ARM crashes on beta
- Top 10 AArch64 and ARM crashes on release
For more information, please visit auto_nag documentation.
| Reporter | ||
Updated•3 years ago
|
| Reporter | ||
Updated•3 years ago
|
Updated•3 years ago
|
Comment 3•3 years ago
|
||
Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Comment 4•3 years ago
|
||
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.
Comment 5•3 years ago
|
||
Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
| Reporter | ||
Updated•3 years ago
|
Comment 6•2 years ago
|
||
Sorry for removing the keyword earlier but there is a recent change in the ranking, so the bug is again linked to a topcrash signature, which matches the following criterion:
- Top 10 AArch64 and ARM crashes on release
For more information, please visit BugBot documentation.
| Reporter | ||
Updated•2 years ago
|
Comment 7•2 years ago
|
||
Based on the topcrash criteria, the crash signatures linked to this bug are not in the topcrash signatures anymore.
For more information, please visit BugBot documentation.
Updated•2 years ago
|
Description
•