ConcurrentModificationException in SystemAlarmDispatcher.hasIntentWithAction() [80346526]

Fixed

Bug

Status Update

No update yet.

Description

tb...@googlemail.com

created issue #1

May 28, 2018 10:35AM

Component used: WorkManager

Version used: 1.0.0-alpha01

Devices/Android versions reproduced on: Android 4.X-6.0

We have a crasch in the WorkManager.
Is there a repository where we can download the code?

Fatal Exception: java.util.ConcurrentModificationException
java.util.ArrayList$ArrayListIterator.next (ArrayList.java:573)
androidx.work.impl.background.systemalarm.SystemAlarmDispatcher.hasIntentWithAction (SourceFile:241)
androidx.work.impl.background.systemalarm.SystemAlarmDispatcher.add (SourceFile:125)
androidx.work.impl.background.systemalarm.SystemAlarmDispatcher$AddRunnable.run (SourceFile:289)
android.os.Handler.handleCallback (Handler.java:733)
android.os.Handler.dispatchMessage (Handler.java:95)
android.os.Looper.loop (Looper.java:136)
android.app.ActivityThread.main (ActivityThread.java:5584)
java.lang.reflect.Method.invokeNative (Method.java)
java.lang.reflect.Method.invoke (Method.java:515)
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1268)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1084)
dalvik.system.NativeStart.main (NativeStart.java)

Comments

ti...@gmail.com <ti...@gmail.com> #2May 29, 2018 10:01PM

A couple of questions:

1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?

su...@google.com <su...@google.com> May 30, 2018 05:10PM

Assigned to su...@google.com.

su...@google.com <su...@google.com> #3May 30, 2018 08:52PM

Marked as fixed.

Tested on Android 12 Emulator with custom executor, but cannot repro this issue.

an...@gmail.com <an...@gmail.com> #4Jun 6, 2018 07:43PM

Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
Dynamic features are not used in the application.

As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.

su...@google.com <su...@google.com> #5Jun 6, 2018 07:45PM

Hmm, I feel the crash might be something related to separate/secondary process.

I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.

Issue 80346526