firebase-android-sdk: java.util.concurrent.RejectedExecutionException in Crashlytics
Describe your environment
- Android Studio version: 4.0.1
- Firebase Component: Crashlytics
- Component version: 17.2.1
Describe the problem
Crashes on Huawei devices with api levels 24, 26, 27, 28, 29
java.util.concurrent.RejectedExecutionException: at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution (ThreadPoolExecutor.java:2104) at java.util.concurrent.ThreadPoolExecutor.reject (ThreadPoolExecutor.java:848) at java.util.concurrent.ThreadPoolExecutor.execute (ThreadPoolExecutor.java:1413) at java.util.concurrent.Executors$DelegatedExecutorService.execute (Executors.java:624) at com.google.android.gms.tasks.zzc.zza at com.google.android.gms.tasks.zzq.zza at com.google.android.gms.tasks.zzu.zza at com.google.android.gms.tasks.zze.run at java.util.concurrent.ThreadPoolExecutor.processTask (ThreadPoolExecutor.java:1187) at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1152) at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641) at com.google.firebase.crashlytics.internal.common.ExecutorUtils$1$1.onRun (ExecutorUtils.java:60) at com.google.firebase.crashlytics.internal.common.BackgroundPriorityRunnable.run (BackgroundPriorityRunnable.java:27) at java.lang.Thread.run (Thread.java:784)
Steps to reproduce
I was not able to reproduce it locally but it happens regularly in production.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 20 (7 by maintainers)
Hi everyone - We’ve just released Firebase Crashlytics v.17.3.0 which should address this problem. Please try it out and let me know how it goes for you. 😃
Hi everyone, an update from our side. We seem to have solved this with an update which essentially changed the following:
firebase-analytics:17.6.0->17.5.0firebase-messaging:20.3.0->20.2.0android:priorityattribute from an intent filter registered in a BroadcastReceiver, since we thought this could affect the scheduling of Crashlytics tasks in some way.We used to see this crash ~twice/hour and we’ve now been live for 3.5 days and not a single occurrence so far. However, we’re not sure which of the actions did the trick
This crash probably unrelated to screen rotation, my app has fixed screen orientation.
Hi folks - wanted to just ping this thread and let you know we’re looking into this and I’ll let you know when I have more information.