ArrayIndexOutOfBoundsException at ja.burhanrashid52.photoeditor.BitmapUtil.removeTransparency (BitmapUtil.java:46)
See original GitHub issueI have crash reports of ArrayIndexOutOfBoundsException through Crashlytics in my app:
java.lang.RuntimeException: at android.os.AsyncTask$3.done (AsyncTask.java:353) at java.util.concurrent.FutureTask.finishCompletion (FutureTask.java:383) at java.util.concurrent.FutureTask.setException (FutureTask.java:252) at java.util.concurrent.FutureTask.run (FutureTask.java:271) at android.os.AsyncTask$SerialExecutor$1.run (AsyncTask.java:245) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1162) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:636) at java.lang.Thread.run (Thread.java:764) Caused by: java.lang.ArrayIndexOutOfBoundsException: at ja.burhanrashid52.photoeditor.BitmapUtil.removeTransparency (BitmapUtil.java:46) at ja.burhanrashid52.photoeditor.PhotoEditor$6$1.doInBackground (PhotoEditor.java:743) at ja.burhanrashid52.photoeditor.PhotoEditor$6$1.doInBackground (PhotoEditor.java:730) at android.os.AsyncTask$2.call (AsyncTask.java:333) at java.util.concurrent.FutureTask.run (FutureTask.java:266) at android.os.AsyncTask$SerialExecutor$1.run (AsyncTask.java:245) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1162) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:636) at java.lang.Thread.run (Thread.java:764)
Unfortunately, I cannot provide any more information at the moment other than this.
I am using implementation 'ja.burhanrashid52:photoeditor:1.0.0'
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:12 (3 by maintainers)
Top GitHub Comments
Happened to see another occurrence in the production instance of my app
Looks like a bug in the code snippet below (taken from
BitmapUtil.removeTransparency
)for (int x = firstX; x < source.getHeight(); x++) {
should befor (int x = firstX; x < source.getWidth(); x++) {
Sorry, can’t reproduce it. Already using the fix in the production instance of my app. Will try to update here if I see this issue again.