Closed Bug 1849795 Opened 2 years ago Closed 11 months ago

Crash in [@ android.app.RemoteServiceException: at android.app.ActivityThread$H.handleMessage(ActivityThread.java)] The given region must intersect with the Bitmap's dimensions

Categories

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

Unspecified
Android
defect

Tracking

()

RESOLVED INVALID
Tracking Status
firefox116 --- affected
firefox117 --- affected
firefox118 --- affected

People

(Reporter: cpeterson, Unassigned)

References

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/83d6a0eb-7976-4074-ada2-30d5d0230823

[@ android.app.RemoteServiceException: at android.app.ActivityThread$H.handleMessage(ActivityThread.java)] is a generic crash signature (meta bug 1774678), but we have a spike in crashes with a new exception reason IllegalArgumentException: The given region must intersect with the Bitmap's dimensions. starting in 115.

Java stack trace:

android.app.RemoteServiceException: Bad notification posted from package org.mozilla.firefox: Couldn't inflate contentViewsjava.lang.IllegalArgumentException: The given region must intersect with the Bitmap's dimensions.
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1881)
	at android.os.Handler.dispatchMessage(Handler.java:105)
	at android.os.Looper.loop(Looper.java:164)
	at android.app.ActivityThread.main(ActivityThread.java:6942)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
Crash Signature: [@ android.app.RemoteServiceException: at android.app.ActivityThread$H.handleMessage(ActivityThread.java)] → [@ android.app.RemoteServiceException: at android.app.ActivityThread$H.handleMessage(ActivityThread.java)] [@ android.app.RemoteServiceException: at android.app.ActivityThread$H.handleMessage(Unknown Source:335)] [@ android.app.RemoteServiceException: a…

The bug is 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.

Keywords: topcrash

The severity field is not set for this bug.
:jonalmeida, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(jonalmeida942)

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.

Keywords: topcrash
Severity: -- → S2
Priority: -- → P2
Flags: needinfo?(jonalmeida942)
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.