JobScheduler 100 crash [111569265]

Fixed

Bug

Status Update

No update yet.

Description

hu...@gmail.com

created issue #1

Jul 18, 2018 08:41AM

Component used: work-runtime, work-firebase
Version used: 1.0.0-alpha04
Devices/Android versions reproduced on: AVD Pixel 2 27

Our setup:

`
<provider
android:name="androidx.work.impl.WorkManagerInitializer"
android:enabled="false"
tools:ignore="ExportedContentProvider" />
`

`
val wmConfig = Configuration
.Builder()
.setMaxSchedulerLimit(95)
.build()
WorkManager.initialize(ctx, wmConfig)
`

It's not always crashes.

We are scheduling multiple jobs chains. Each chain is a tree where we utilize input/outputs, where the last job depends on all the leafs of the tree. We build this tree only once, no recheduling inside Workers.

Comments

hu...@gmail.com <hu...@gmail.com> #2Jul 18, 2018 09:02AM

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?

ra...@google.com <ra...@google.com> #3Jul 18, 2018 04:18PM

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

hu...@gmail.com <hu...@gmail.com> #4Jul 19, 2018 06:32AM

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.

hu...@gmail.com <hu...@gmail.com> #5Jul 19, 2018 06:33AM

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.

ra...@google.com <ra...@google.com> #6Jul 19, 2018 08:33PM

On the contrary, there was no separate process before, when crashes started.

In the new build (with the aforementioned changes) I can see SIGSEGV crash, but only one instead of dozens and it has a bit different backtrace:

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
liblanguage_id_jni.so (offset 0x11e000)

backtrace:
  #00  pc 000000000003c7c0  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 000000000003b960  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 000000000003bb48  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 000000000003bafc  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000036c98  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000032714  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000031cac  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/split_config.arm64_v8a.apk!lib/arm64-v8a/liblanguage_id_jni.so (offset 0x11e000)
  #00  pc 0000000000057438  /data/app/azagroup.reedy-mF7zTu2bv_ELlbFArwNgqA==/oat/arm64/base.odex (offset 0x57000)

ra...@google.com <ra...@google.com> #7Jul 19, 2018 09:36PM

FYI, ML Kit launched a new language ID SDK in the latest release, which uses a new language ID model. https://developers.google.com/ml-kit/release-notes#august_11_2021

Could you try the new SDK version(17.0.0) to check if you can still repro this native crash? Thanks!

hu...@gmail.com <hu...@gmail.com> #8Jul 20, 2018 06:53AM

Thank you, I'll try it and check.

ra...@google.com <ra...@google.com> Jul 20, 2018 09:29PM

Assigned to ra...@google.com.

ra...@google.com <ra...@google.com> #9Jul 23, 2018 09:34PM

Status: Won't Fix (Not Reproducible)

Hello. I have similar experience.

I'm using mlkit-language 16.1.1
I didnot meet this error until using AGP 4.2
I can get this error since using AGP 7.0
This error raised on Release build only(minimized by R8)
This error raised without obfuscation.

su...@google.com <su...@google.com> #10Jul 23, 2018 09:47PM

Also I found there is a post which presents same issue on stackoverflow.

https://stackoverflow.com/questions/68832304/mlkit-translate-sdk-crashes-in-release-build

hu...@gmail.com <hu...@gmail.com> #11Jul 24, 2018 08:01PM

I created reproducible project.

$ git clone https://github.com/ganadist/VersionCodeDemo -b mlkit_agp7 mlkit_agp7
$ cd mlkit_agp7
$ ./gradlew :app:pPRUA
$ adb install app/build/outputs/universal_apk/productionRelease/app-production-release-universal.apk
$ adb shell am start -n com.example.myapplication/.MainActivity

$ adb logcat -b crash -d
10-19 19:41:49.844 17810 17810 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x7acf9d733c in tid 17810 (e.myapplication), pid 17810 (e.myapplication)
10-19 19:41:50.473 17849 17849 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
10-19 19:41:50.473 17849 17849 F DEBUG   : Build fingerprint: 'google/crosshatch/crosshatch:12/SPB5.210812.002/7671067:user/release-keys'
10-19 19:41:50.473 17849 17849 F DEBUG   : Revision: 'MP1.0'
10-19 19:41:50.473 17849 17849 F DEBUG   : ABI: 'arm64'
10-19 19:41:50.473 17849 17849 F DEBUG   : Timestamp: 2021-10-19 19:41:49.903736988+0900
10-19 19:41:50.473 17849 17849 F DEBUG   : Process uptime: 0s
10-19 19:41:50.473 17849 17849 F DEBUG   : Cmdline: com.example.myapplication
10-19 19:41:50.474 17849 17849 F DEBUG   : pid: 17810, tid: 17810, name: e.myapplication  >>> com.example.myapplication <<<
10-19 19:41:50.474 17849 17849 F DEBUG   : uid: 10240
10-19 19:41:50.474 17849 17849 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x7acf9d733c
10-19 19:41:50.474 17849 17849 F DEBUG   :     x0  0000000000000000  x1  00000000000008fc  x2  0000007a76760c71  x3  0000000000000000
10-19 19:41:50.474 17849 17849 F DEBUG   :     x4  0000000000000010  x5  0000007ba4db49d0  x6  0000007b34dc3680  x7  3de38e3900000608
10-19 19:41:50.474 17849 17849 F DEBUG   :     x8  0000007bb4dbedf0  x9  0000007acf9db2aa  x10 0000000000000000  x11 0000007acf9d6640
10-19 19:41:50.474 17849 17849 F DEBUG   :     x12 0000000000000009  x13 0000000000000000  x14 0000000000000061  x15 00000000ebad6a89
10-19 19:41:50.474 17849 17849 F DEBUG   :     x16 0000007a767cfef8  x17 0000007d9a564b40  x18 0000007da3830000  x19 0000007feaf56a08
10-19 19:41:50.474 17849 17849 F DEBUG   :     x20 0000000000000000  x21 0000007ba4da50b0  x22 0000007bb4dbedf0  x23 0000007ba4da50b8
10-19 19:41:50.474 17849 17849 F DEBUG   :     x24 0000000000000009  x25 000000000000067e  x26 0000000000000012  x27 0000000000000008
10-19 19:41:50.474 17849 17849 F DEBUG   :     x28 0000007b64dc8440  x29 0000000000000000
10-19 19:41:50.474 17849 17849 F DEBUG   :     lr  0000007a7678a964  sp  0000007feaf56810  pc  0000007a7678b7c0  pst 0000000060000000
10-19 19:41:50.474 17849 17849 F DEBUG   : backtrace:
10-19 19:41:50.474 17849 17849 F DEBUG   :       #00 pc 000000000003c7c0  /data/app/~~mHaMq-e9ocbm9UfYnkCGkQ==/com.example.myapplication-HgG9vkluwDDO1K78-Vzr0A==/lib/arm64/liblanguage_id_jni.so (BuildId: 859ec0ec2000a39e6ae8ed42e1704f46)
10-19 19:41:50.474 17849 17849 F DEBUG   :       #01 pc 000000000003b960  /data/app/~~mHaMq-e9ocbm9UfYnkCGkQ==/com.example.myapplication-HgG9vkluwDDO1K78-Vzr0A==/lib/arm64/liblanguage_id_jni.so (BuildId: 859ec0ec2000a39e6ae8ed42e1704f46)
10-19 19:41:50.474 17849 17849 F DEBUG   :       #02 pc 000000000003bb48  /data/app/~~mHaMq-e9ocbm9UfYnkCGkQ==/com.example.myapplication-HgG9vkluwDDO1K78-Vzr0A==/lib/arm64/liblanguage_id_jni.so (BuildId: 859ec0ec2000a39e6ae8ed42e1704f46)
10-19 19:41:50.474 17849 17849 F DEBUG   :       #03 pc 000000000003bafc  /data/app/~~mHaMq-e9ocbm9UfYnkCGkQ==/com.example.myapplication-HgG9vkluwDDO1K78-Vzr0A==/lib/arm64/liblanguage_id_jni.so (BuildId: 859ec0ec2000a39e6ae8ed42e1704f46)
10-19 19:41:50.474 17849 17849 F DEBUG   :       #04 pc 0000000000036c98  /data/app/~~mHaMq-e9ocbm9UfYnkCGkQ==/com.example.myapplication-HgG9vkluwDDO1K78-Vzr0A==/lib/arm64/liblanguage_id_jni.so (BuildId: 859ec0ec2000a39e6ae8ed42e1704f46)
10-19 19:41:50.474 17849 17849 F DEBUG   :       #05 pc 00000000000324a4  /data/app/~~mHaMq-e9ocbm9UfYnkCGkQ==/com.example.myapplication-HgG9vkluwDDO1K78-Vzr0A==/lib/arm64/liblanguage_id_jni.so (BuildId: 859ec0ec2000a39e6ae8ed42e1704f46)
10-19 19:41:50.474 17849 17849 F DEBUG   :       #06 pc 0000000000031b5c  /data/app/~~mHaMq-e9ocbm9UfYnkCGkQ==/com.example.myapplication-HgG9vkluwDDO1K78-Vzr0A==/lib/arm64/liblanguage_id_jni.so (Java_com_google_mlkit_nl_languageid_internal_LanguageIdentificationJni_nativeIdentifyLanguage+100) (BuildId: 859ec0ec2000a39e6ae8ed42e1704f46)

But after downgrade to AGP 4.2, crash is not reproducible.

$ git clone https://github.com/ganadist/VersionCodeDemo -b mlkit_agp42 mlkit_agp42
$ cd mlkit_agp42
$ ./gradlew :app:pPRUA
$ adb install app/build/outputs/universal_apk/productionRelease/app-production-release-universal.apk
$ adb shell am start -n com.example.myapplication/.MainActivity

Also, I tried to disable inline optimizers on R8 with AGP 7.0, and crash is not reproducible.

$ git clone https://github.com/ganadist/VersionCodeDemo -b mlkit_agp7_r8_disable_inline_optimizer  mlkit_agp7_r8
$ cd mlkit_agp7_r8
$ ./gradlew :app:pPRUA
$ adb install app/build/outputs/universal_apk/productionRelease/app-production-release-universal.apk
$ adb shell am start -n com.example.myapplication/.MainActivity

hu...@gmail.com <hu...@gmail.com> #12Jul 25, 2018 09:18PM

I tried the repro steps but got a NPE when I run ./gradlew :app:pPRUA

FAILURE: Build failed with an exception.

* What went wrong:
java.lang.NullPointerException
> java.lang.NullPointerException (no error message)

Could you also check if this is reproducible on 17.0.0 or 17.0.1? If yes, could you attach the full log that I can take a look? Thanks!

MyApplication.7z

825 KB

Download

su...@google.com <su...@google.com> Jul 25, 2018 09:58PM

Status: Assigned (reopened)

su...@google.com <su...@google.com> #13Jul 30, 2018 06:08PM

Reassigned to su...@google.com.

Here are gradle build scan logs for each branches.
All builds were clean build, and disabled build cache.

mlkit_agp7 : https://scans.gradle.com/s/qrymdqfzwokbq
mlkit_agp42 : https://scans.gradle.com/s/b6644hzfyfhaw
mlkit_agp7_r8_disable_inline_optimizer : https://scans.gradle.com/s/c6h5hy2nxod4u
- You can see R8 debug mode on build log : https://scans.gradle.com/s/c6h5hy2nxod4u/console-log#L95

Also, I pushed to update MLKit Language Id version 17.0.1 on mlkit17_agp7 branch And here is gradle build scan

https://scans.gradle.com/s/ytaa2kkbp5vc4
- Here is version of com.google.mlkit:language-id

And here is crash log after apply 17.0.1
You can see that BuildId of liblanguage_id_l2c_jni.so was changed from 859ec0ec2000a39e6ae8ed42e1704f46 to be6e59455cc10135330c93acdebfc121

10-20 03:07:24.522 24587 24628 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x7acf995426 in tid 24628 (pool-3-thread-3), pid 24587 (e.myapplication)
10-20 03:07:25.190 24710 24710 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
10-20 03:07:25.190 24710 24710 F DEBUG   : Build fingerprint: 'google/crosshatch/crosshatch:12/SPB5.210812.002/7671067:user/release-keys'
10-20 03:07:25.190 24710 24710 F DEBUG   : Revision: 'MP1.0'
10-20 03:07:25.190 24710 24710 F DEBUG   : ABI: 'arm64'
10-20 03:07:25.190 24710 24710 F DEBUG   : Timestamp: 2021-10-20 03:07:24.583346246+0900
10-20 03:07:25.190 24710 24710 F DEBUG   : Process uptime: 0s
10-20 03:07:25.190 24710 24710 F DEBUG   : Cmdline: com.example.myapplication
10-20 03:07:25.190 24710 24710 F DEBUG   : pid: 24587, tid: 24628, name: pool-3-thread-3  >>> com.example.myapplication <<<
10-20 03:07:25.190 24710 24710 F DEBUG   : uid: 10240
10-20 03:07:25.190 24710 24710 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x7acf995426
10-20 03:07:25.190 24710 24710 F DEBUG   :     x0  0000007b54da9d30  x1  0000007d9a5fe7cc  x2  0000000000000000  x3  0000000000000010
10-20 03:07:25.190 24710 24710 F DEBUG   :     x4  0000000000000000  x5  0000007c34dbc79c  x6  0000002f0000083b  x7  000003c300002dd5
10-20 03:07:25.190 24710 24710 F DEBUG   :     x8  0000000000000001  x9  0000000000000004  x10 0000000000000010  x11 0000000000000000
10-20 03:07:25.190 24710 24710 F DEBUG   :     x12 0000000000000000  x13 000000000000217e  x14 0000007acf9932a8  x15 000000000000217e
10-20 03:07:25.190 24710 24710 F DEBUG   :     x16 0000000000000000  x17 0000007d9a564c78  x18 0000007a6ef18000  x19 0000007c34dbc580
10-20 03:07:25.190 24710 24710 F DEBUG   :     x20 0000007ca4dc7170  x21 0000007ca4dc7800  x22 0000007ca4dc71e0  x23 0000000000000000
10-20 03:07:25.190 24710 24710 F DEBUG   :     x24 0000000000000018  x25 0000000000000007  x26 0000000000000006  x27 0000000000000004
10-20 03:07:25.190 24710 24710 F DEBUG   :     x28 0000007ca4dc7090  x29 0000007cb4da9940
10-20 03:07:25.190 24710 24710 F DEBUG   :     lr  0000007a770a9624  sp  0000007a6f7de9c0  pc  0000007a770a96a8  pst 0000000020000000
10-20 03:07:25.190 24710 24710 F DEBUG   : backtrace:
10-20 03:07:25.190 24710 24710 F DEBUG   :       #00 pc 00000000000386a8  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/lib/arm64/liblanguage_id_l2c_jni.so (BuildId: be6e59455cc10135330c93acdebfc121)
10-20 03:07:25.190 24710 24710 F DEBUG   :       #01 pc 00000000000388a0  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/lib/arm64/liblanguage_id_l2c_jni.so (BuildId: be6e59455cc10135330c93acdebfc121)
10-20 03:07:25.190 24710 24710 F DEBUG   :       #02 pc 00000000000844a0  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/lib/arm64/liblanguage_id_l2c_jni.so (BuildId: be6e59455cc10135330c93acdebfc121)
10-20 03:07:25.190 24710 24710 F DEBUG   :       #03 pc 000000000008783c  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/lib/arm64/liblanguage_id_l2c_jni.so (BuildId: be6e59455cc10135330c93acdebfc121)
10-20 03:07:25.190 24710 24710 F DEBUG   :       #04 pc 0000000000035fc4  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/lib/arm64/liblanguage_id_l2c_jni.so (BuildId: be6e59455cc10135330c93acdebfc121)
10-20 03:07:25.190 24710 24710 F DEBUG   :       #05 pc 0000000000034954  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/lib/arm64/liblanguage_id_l2c_jni.so (BuildId: be6e59455cc10135330c93acdebfc121)
10-20 03:07:25.190 24710 24710 F DEBUG   :       #06 pc 00000000000340e8  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/lib/arm64/liblanguage_id_l2c_jni.so (Java_com_google_mlkit_nl_languageid_internal_ThickLanguageIdentifier_nativeIdentifyPossibleLanguages+108) (BuildId: be6e59455cc10135330c93acdebfc121)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #07 pc 00000000002d9a44  /apex/com.android.art/lib64/libart.so (art_quick_generic_jni_trampoline+148) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #08 pc 000000000020a700  /apex/com.android.art/lib64/libart.so (nterp_helper+5648) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #09 pc 00000000000cd0dc  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/oat/arm64/base.vdex
10-20 03:07:25.191 24710 24710 F DEBUG   :       #10 pc 000000000020a044  /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #11 pc 00000000000ccfa8  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/oat/arm64/base.vdex
10-20 03:07:25.191 24710 24710 F DEBUG   :       #12 pc 0000000000557cb4  /system/framework/arm64/boot-framework.oat (android.os.Binder.transact+148) (BuildId: 43a571a0ad85d6451b47016336a541ecb0eb12bb)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #13 pc 000000000020b53c  /apex/com.android.art/lib64/libart.so (nterp_helper+9292) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #14 pc 00000000000b7aba  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/oat/arm64/base.vdex
10-20 03:07:25.191 24710 24710 F DEBUG   :       #15 pc 000000000020a044  /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #16 pc 00000000000a7496  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/oat/arm64/base.vdex
10-20 03:07:25.191 24710 24710 F DEBUG   :       #17 pc 000000000020a044  /apex/com.android.art/lib64/libart.so (nterp_helper+3924) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #18 pc 00000000000a7360  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/oat/arm64/base.vdex
10-20 03:07:25.191 24710 24710 F DEBUG   :       #19 pc 000000000020ae64  /apex/com.android.art/lib64/libart.so (nterp_helper+7540) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #20 pc 000000000009e46c  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/oat/arm64/base.vdex
10-20 03:07:25.191 24710 24710 F DEBUG   :       #21 pc 000000000020ae64  /apex/com.android.art/lib64/libart.so (nterp_helper+7540) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #22 pc 00000000000d33d6  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/oat/arm64/base.vdex
10-20 03:07:25.191 24710 24710 F DEBUG   :       #23 pc 000000000020ae64  /apex/com.android.art/lib64/libart.so (nterp_helper+7540) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #24 pc 000000000009df0a  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/oat/arm64/base.vdex
10-20 03:07:25.191 24710 24710 F DEBUG   :       #25 pc 0000000000209124  /apex/com.android.art/lib64/libart.so (nterp_helper+52) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #26 pc 000000000009e350  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/oat/arm64/base.vdex
10-20 03:07:25.191 24710 24710 F DEBUG   :       #27 pc 000000000037b9ac  /apex/com.android.art/javalib/arm64/boot.oat (java.util.concurrent.ThreadPoolExecutor.runWorker+988) (BuildId: ab2bf4ec264efdb6c452a238be38fe624de826b8)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #28 pc 00000000003751d4  /apex/com.android.art/javalib/arm64/boot.oat (java.util.concurrent.ThreadPoolExecutor$Worker.run+68) (BuildId: ab2bf4ec264efdb6c452a238be38fe624de826b8)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #29 pc 000000000020aec4  /apex/com.android.art/lib64/libart.so (nterp_helper+7636) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #30 pc 000000000009e370  /data/app/~~KjjULZV48O7KSOgOP1wYNQ==/com.example.myapplication-vFUidUPTjaGg4oo3SRAYJw==/oat/arm64/base.vdex
10-20 03:07:25.191 24710 24710 F DEBUG   :       #31 pc 00000000001bf35c  /apex/com.android.art/javalib/arm64/boot.oat (java.lang.Thread.run+76) (BuildId: ab2bf4ec264efdb6c452a238be38fe624de826b8)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #32 pc 00000000002d0164  /apex/com.android.art/lib64/libart.so (art_quick_invoke_stub+548) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #33 pc 000000000031ccac  /apex/com.android.art/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+156) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #34 pc 00000000003cf8a0  /apex/com.android.art/lib64/libart.so (art::JValue art::InvokeVirtualOrInterfaceWithJValues<art::ArtMethod*>(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, art::ArtMethod*, jvalue const*)+380) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #35 pc 0000000000460894  /apex/com.android.art/lib64/libart.so (art::Thread::CreateCallback(void*)+992) (BuildId: cdecb8dde1264c9871695c29854aa3b1)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #36 pc 00000000000b1910  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+264) (BuildId: ba489d4985c0cf173209da67405662f9)
10-20 03:07:25.191 24710 24710 F DEBUG   :       #37 pc 00000000000513f0  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: ba489d4985c0cf173209da67405662f9)

hu...@gmail.com <hu...@gmail.com> #14Jul 31, 2018 08:58AM

Cross-posted on R8 issue tracker. https://issuetracker.google.com/issues/203573699

hu...@gmail.com <hu...@gmail.com> #15Aug 1, 2018 08:08AM

Hi,

Looks like we figured out the root cause in b/203573699

For temporary workarounds for the existing SDKs, you need to add this rule

-keep class com.google.mlkit.nl.languageid.internal.LanguageIdentificationJni { *; }

for language-id 16.1.1, and add this rule

-keep class com.google.mlkit.nl.languageid.internal.ThickLanguageIdentifier { *; }

for version language-id 17.0.0+ for the newer model.

We'll fix this issue in the upcoming release so that you'll not need these workarounds in the future release.

Thanks a lot for reporting this issue!

Xiaomi.txt

471 KB

View

Download

Geymotion.txt

568 KB

View

Download

su...@google.com <su...@google.com> #16Aug 1, 2018 06:18PM

Added workarounds in Known issues section in public docs.

hu...@gmail.com <hu...@gmail.com> #17Aug 2, 2018 10:49AM

https://issuetracker.google.com/issues/250610583

https://issuetracker.google.com/issues/250609756

https://issuetracker.google.com/issues/250609759

https://issuetracker.google.com/issues/250610272

https://issuetracker.google.com/issues/250610273

https://issuetracker.google.com/issues/250610276

https://issuetracker.google.com/issues/250610278

https://issuetracker.google.com/issues/250610593

https://issuetracker.google.com/issues/250610280

https://issuetracker.google.com/issues/250610923

https://issuetracker.google.com/issues/250610282

https://issuetracker.google.com/issues/250611106

https://issuetracker.google.com/issues/250610598

https://issuetracker.google.com/issues/250611463

https://issuetracker.google.com/issues/250611111

https://issuetracker.google.com/issues/250610933

https://issuetracker.google.com/issues/250610935

https://issuetracker.google.com/issues/250611113

https://issuetracker.google.com/issues/250610937

https://issuetracker.google.com/issues/250611116

https://issuetracker.google.com/issues/250611466

https://issuetracker.google.com/issues/250612724

https://issuetracker.google.com/issues/250612604

https://issuetracker.google.com/issues/250612726

https://issuetracker.google.com/issues/250611471

https://issuetracker.google.com/issues/250177858

https://issuetracker.google.com/issues/250172577

https://www.endezo-it.com/2022/10/the-dark-event-of-indonesian-football.html

https://www.49erssports.com/2022/10/kanjuruhan-tragedy-arema-fc-management.html

https://one-piece-red-full-movie-english.webflow.io/

https://documenter.getpostman.com/view/21828632/2s83tJGAat

Xiaomi alpha06.txt

540 KB

View

Download

hu...@gmail.com <hu...@gmail.com> #18Aug 2, 2018 10:50AM

↑ This is Genymotion not Xiaomi log

ra...@google.com <ra...@google.com> #19Aug 2, 2018 10:38PM

Status: Won't Fix (Not Reproducible)

I tried to reproduce this on a Genymotion emulator as well (on alpha04 and alpha06) on API 26. I cannot seem to.
I am marking this as not reproducible.

hu...@gmail.com <hu...@gmail.com> #20Aug 3, 2018 09:59AM

You tried to reproduce it on my example above?

hu...@gmail.com <hu...@gmail.com> #21Aug 3, 2018 10:07AM

How can you not reproduce it when I linked you the code to do so?

VID_20180803_130132.mp4

55 MB

Download

ra...@google.com <ra...@google.com> Aug 3, 2018 10:33PM

Status: Assigned (reopened)

ne...@gmail.com <ne...@gmail.com> #22Aug 7, 2018 10:20AM

Same issue for me, "java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs", on Android 8.0.0 (HTC U11).

Just for my understanding, should we be able to enqueue more than ~100 WorkRequest ?

su...@google.com <su...@google.com> #23Aug 7, 2018 04:23PM

Yes, you should. We found some edge cases where it's possible to schedule more work than allowable by the system and we're working on a fix. Thanks!

ra...@google.com <ra...@google.com> #24Aug 8, 2018 10:10PM

Marked as fixed.

Fixed in

https://android-review.googlesource.com/c/platform/frameworks/support/+/726647.

ra...@google.com <ra...@google.com> #25Aug 8, 2018 10:11PM

A fix should be available in alpha07.

al...@gmail.com <al...@gmail.com> #26Aug 28, 2018 08:56AM

I still got the 100 job crash once using alpha-07

jo...@gmail.com <jo...@gmail.com> #27Aug 28, 2018 11:28PM

Still getting this crash with alpha08 from users (LGE Android 7 and Samsung Android 8):

Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
at android.os.Parcel.readException(Parcel.java:1691)
at android.os.Parcel.readException(Parcel.java:1636)
at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:158)
at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:42)
at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(DT:126)
at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(DT:95)
at androidx.work.impl.Schedulers.schedule(DT:99)
at androidx.work.impl.WorkerWrapper$1.run(DT:263)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)

su...@google.com <su...@google.com> #28Aug 29, 2018 04:01PM

#27, do you mind providing some more info about this? How are you enqueuing your jobs? Do you have a customized WorkManager Configuration (if so, what is it?)? Did you have previously scheduled jobs using alpha07 or earlier or did you enqueue these jobs in alpha08?

Finally, if you can turn on verbose logging through the Configuration options, please send us the logcat using that.

al...@gmail.com <al...@gmail.com> #29Aug 31, 2018 11:54AM

I am en-queuing a OneTimeWorkRequest and listening to it's status change. On status change, I enqueue the same work request (with same tag and other constraints). For some time it runs fine, and then it suddenly crashes complaining of the 100 job crash and also of "WorkerWrapper: Didn't find WorkSpec for id"

Here's the crash log

08-31 17:31:19.892 9930-9985/com.example.agupta15.tryouts E/AndroidRuntime: FATAL EXCEPTION: pool-2-thread-1
Process: com.example.agupta15.tryouts, PID: 9930
java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
at android.os.Parcel.readException(Parcel.java:1692)
at android.os.Parcel.readException(Parcel.java:1637)
at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:158)
at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:42)
at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(SystemJobScheduler.java:126)
at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(SystemJobScheduler.java:95)
at androidx.work.impl.Schedulers.schedule(Schedulers.java:99)
at androidx.work.impl.utils.EnqueueRunnable.scheduleWorkInBackground(EnqueueRunnable.java:114)
at androidx.work.impl.utils.EnqueueRunnable.run(EnqueueRunnable.java:86)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
08-31 17:31:19.893 9930-9930/com.example.agupta15.tryouts D/status worker: id f5c workstatus state = ENQUEUED
08-31 17:31:19.893 9930-9930/com.example.agupta15.tryouts D/WorkManagerUtils: Schedule for Worker Class: Class Job Id: 100100
08-31 17:31:20.016 9930-9993/com.example.agupta15.tryouts E/WorkerWrapper: Didn't find WorkSpec for id 7f9fdb71-1c34-41e0-b012-97be46ecba85
08-31 17:31:20.020 9930-10011/com.example.agupta15.tryouts E/WorkerWrapper: Didn't find WorkSpec for id 6fdcb2ea-1f3c-4238-b175-15c4c4d80ec6

Please ignore the D/ logs (they are my own for debugging)

ra...@google.com <ra...@google.com> #30Aug 31, 2018 05:49PM

@Aloy: Which version of WorkManager are you using? Can you reproduce this issue with alpha08 ?
Also are you changing the default WorkManager Configuration ? Can you please send us a code snippet ?

[Deleted User] <[Deleted User]> #31Sep 3, 2018 06:54AM

For me alpha07 solved the problem.

mi...@sesma.eu <mi...@sesma.eu> #32Sep 6, 2018 11:07AM

This just have happened to a user. We use a unique work to download assets, that can be more than 100. We usually don't have issue but this time the user got:
Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
at android.os.Parcel.readException(Parcel.java:2013)
at android.os.Parcel.readException(Parcel.java:1951)
at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:180)

Device Mi A1 with Android 8.1.0. WorkManager 1.0.0-alpha06

This is the code:
val workers = assets.map { assetModel ->
val data = Data.Builder()
.putString(ASSET_UUID, assetModel.uuid)
.putString(ASSET_URL, assetModel.url)
.putString(ASSET_VERSION, assetModel.version.toString())
.build()
OneTimeWorkRequest.Builder(AssetDownloadWorker::class.java)
.setInputData(data)
.build()
}

val continuation = workManager?.beginUniqueWork(
DOWNLOAD_WORK_NAME + mainUuid,
ExistingWorkPolicy.KEEP,
workers.toList())

su...@google.com <su...@google.com> #33Sep 6, 2018 04:28PM

#32: As noted earlier, this is fixed in newer versions of WorkManager. Please update to the latest version.

al...@gmail.com <al...@gmail.com> #34Sep 12, 2018 06:37AM

Sorry, for the wrong report. Seems to work fine for me now.

[Deleted User] <[Deleted User]> #35Sep 19, 2018 02:23PM

We are using alpha08 and we are still getting this exception. We use the WorkManager to send events to our backend. So we can enque a lot of requests (more than 100) in a short period of time.

We don't know exactly how to reproduce this error but we see in crashlytics that two users are getting this issue lots of times. The date we have about this users and crashes:

User 1, 11 crashes: Android 7.1.1 Nubia NX591J
Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
at android.os.Parcel.readException(Parcel.java:1692)
at android.os.Parcel.readException(Parcel.java:1637)
at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:158)
at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:42)
at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(SystemJobScheduler.java:126)
at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(SystemJobScheduler.java:95)
at androidx.work.impl.Schedulers.schedule(Schedulers.java:99)
at androidx.work.impl.utils.EnqueueRunnable.scheduleWorkInBackground(EnqueueRunnable.java:114)
at androidx.work.impl.utils.EnqueueRunnable.run(EnqueueRunnable.java:86)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)

User 2, 17 crashes: Android 7.0 Asus X008D
Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
at android.os.Parcel.readException(Parcel.java:1691)
at android.os.Parcel.readException(Parcel.java:1636)
at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:158)
at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:42)
at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(SystemJobScheduler.java:126)
at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(SystemJobScheduler.java:95)
at androidx.work.impl.Schedulers.schedule(Schedulers.java:99)
at androidx.work.impl.utils.EnqueueRunnable.scheduleWorkInBackground(EnqueueRunnable.java:114)
at androidx.work.impl.utils.EnqueueRunnable.run(EnqueueRunnable.java:86)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)

ra...@google.com <ra...@google.com> #36Sep 19, 2018 04:18PM

Yeah.. a fix should be available in alpha09 shortly. The relevant issue is

https://issuetracker.google.com/issues/115560696

cr...@supercomputo.mx <cr...@supercomputo.mx> #37Sep 29, 2018 08:38PM

This was happening on android.arch.work:work-runtime:1.0.0-alpha01

This is not still happening on version :1.0.0-alpha09

te...@gmail.com <te...@gmail.com> #38Oct 22, 2018 09:10AM

Hi, this still happening in 1.0.0-alpha09. Only devices with 7 and 8 versions of android are affected.

Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
at android.os.Parcel.readException(Parcel.java:1967)
at android.os.Parcel.readException(Parcel.java:1905)
at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:180)
at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:44)
at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(SystemJobScheduler.java:148)
at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(SystemJobScheduler.java:117)
at androidx.work.impl.Schedulers.schedule(Schedulers.java:99)
at androidx.work.impl.utils.EnqueueRunnable.scheduleWorkInBackground(EnqueueRunnable.java:114)
at androidx.work.impl.utils.EnqueueRunnable.run(EnqueueRunnable.java:86)
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)

te...@gmail.com <te...@gmail.com> #39Oct 22, 2018 09:17AM

The code, that i used:

class App : MultiDexApplication() {

override fun onCreate() {
super.onCreate()
Job.schedule()
}
}

class Job(ctx: Context, params: WorkerParameters) : Worker(ctx, params) {

override fun doWork(): Worker.Result {
Log.d("-------------------Job is done!--------------------")
return Result.SUCCESS
}

companion object {
private const val TAG = "my_job"

fun schedule() {
val workManager = WorkManager.getInstance()
val work = PeriodicWorkRequest.Builder(Job::class.java, 1, DAYS).addTag(TAG).build()
workManager.enqueueUniquePeriodicWork(TAG, KEEP, work)
}
}
}

mi...@sesma.eu <mi...@sesma.eu> #40Oct 22, 2018 09:30AM

In our case, seems that alpha-10 is not having this crash anymore. After four days in production no events have happened.

te...@gmail.com <te...@gmail.com> #41Oct 22, 2018 09:33AM

Ok I'm updated to alpha10, and watching for statistics now.

so...@gmail.com <so...@gmail.com> #42Oct 26, 2018 10:05PM

Updated to alpha10 and the crash persisted. Doesn't seem to be fixed, so reverting my app back to firebase jobdispatcher.

ad...@gmail.com <ad...@gmail.com> #43Dec 19, 2018 08:38AM

We had this problem on aplha08, aplha09 and now on alpha11. On alpha11 it is happening less than before, but there are still many crashes.

I'm removing WorkManager from our project and getting back to JobScheduler.

I can't believe that Google is not able to fix a base/core issue in this library for 11 versions straight, it is totally unusable with this bug.

Is there a way we can raise this ticket to someone more competent that is able to solve this problem???

Such a shame Google...

ra...@google.com <ra...@google.com> #44Dec 19, 2018 06:11PM

We have fixed all known issues around this. If you are still seeing this, feel free to send us a stacktrace and a sample app that reproduces the problem.

ad...@gmail.com <ad...@gmail.com> #45Dec 20, 2018 09:33PM

Sorry, I could not reproduce the issue myself. I lost a whole day trying to reproduce the issue and I could not do it, but it does not mean that the crash is not happening.

On 50K users using the app (with alpha11 library), we see that around 0.1% (50) of them have these crashes. It only happens on Android version 7 and 8.

We had a bigger crash rate before upgrading to alpha11, but the bug is still happening.

The only traces I have are these from Fabric:

Android 7
Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
at android.os.Parcel.readException(Parcel.java:1701)
at android.os.Parcel.readException(Parcel.java:1646)
at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:158)
at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:42)
at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(Unknown Source:148)
at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(Unknown Source:117)
at androidx.work.impl.Schedulers.schedule(Unknown Source:99)
at androidx.work.impl.WorkManagerImpl.rescheduleEligibleWork(Unknown Source:550)
at androidx.work.impl.utils.ForceStopRunnable.run(Unknown Source:74)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:762)

Android 7
Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
at android.os.Parcel.readException(Parcel.java:1691)
at android.os.Parcel.readException(Parcel.java:1636)
at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:158)
at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:42)
at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(Unknown Source:148)
at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(Unknown Source:117)
at androidx.work.impl.Schedulers.schedule(Unknown Source:99)
at androidx.work.impl.WorkManagerImpl.rescheduleEligibleWork(Unknown Source:550)
at androidx.work.impl.utils.ForceStopRunnable.run(Unknown Source:74)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)

Android 8
Fatal Exception: java.lang.IllegalStateException: Apps may not schedule more than 100 distinct jobs
at android.os.Parcel.readException(Parcel.java:1975)
at android.os.Parcel.readException(Parcel.java:1913)
at android.app.job.IJobScheduler$Stub$Proxy.schedule(IJobScheduler.java:180)
at android.app.JobSchedulerImpl.schedule(JobSchedulerImpl.java:44)
at androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal(Unknown Source:148)
at androidx.work.impl.background.systemjob.SystemJobScheduler.schedule(Unknown Source:117)
at androidx.work.impl.Schedulers.schedule(Unknown Source:99)
at androidx.work.impl.WorkManagerImpl.rescheduleEligibleWork(Unknown Source:550)
at androidx.work.impl.utils.ForceStopRunnable.run(Unknown Source:74)
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)

It is happening on a wide range of devices (some of them):

Samsung Galaxy S7 (herolte),
Samsung Galaxy S7 (heroltebmc), Android 7.0
Samsung Galaxy Note5 (noblelte), Android 7.0
Samsung Galaxy S6 (zeroflte), Android 7.0
Samsung Galaxy S7 edge (hero2lte), Android 8.0
Motorola Moto G (5th Gen) (cedric), Android 8.1
Motorola Moto G(4) Plus (athene_f), Android 7.0
LGE V20 (elsa), Android 8.0
LGE LG K20 (lv517n), Android 7.0
dream2qltesq, Android 7.0
Huawei 荣耀畅玩 6X (HWBLN-H), Android 7.0
Sony Xperia Z5 (SO-01H), Android 7.0
Sony Xperia XZ Premium (SO-04J), Android 8.0

ra...@google.com <ra...@google.com> #46Dec 20, 2018 10:05PM

I think what might be happening is that some of the already scheduled jobs, may be stuck in a certain state.
You might want to push an update on the next version of your app, where you can cancelAllWork(), and reschedule all the Workers you need.

ad...@gmail.com <ad...@gmail.com> #47Jan 8, 2019 08:38PM

I have tried with cancelAllWorkByTag using the tag we used to create the jobs in the newest staged release but it did not help. We are still seeing the same crashes. We have also updated the lib to the latest (beta01) version.

ra...@google.com <ra...@google.com> #48Jan 9, 2019 12:21AM

cancelAllWorkByTag() only cancels work with tag.To be sure, you could cancelAllWork() [

https://developer.android.com/reference/androidx/work/WorkManager.html#cancelAllWork()]
That way you are guaranteed to start from a clean slate, and then you can reschedule your work. Also, are you using a custom configuration when instantiating WorkManager ?

ad...@gmail.com <ad...@gmail.com> #49Jan 9, 2019 06:58PM

Yes, but we used a static constant in NotificationWorker.class to initialize it and used the same constant to cancel the work, so all workers should be stopped.

Here is the code:

WorkManager.getInstance().cancelAllWorkByTag(NotificationWorker.TAG);

PeriodicWorkRequest.Builder notificationsWorkBuilder = new PeriodicWorkRequest.Builder(NotificationWorker.class, NOTIFICATIONS_PERIOD, TimeUnit.MILLISECONDS);
notificationsWorkBuilder.addTag(NotificationWorker.TAG);
PeriodicWorkRequest notificationWork = notificationsWorkBuilder.build();
WorkManager.getInstance().enqueueUniquePeriodicWork(NotificationWorker.TAG, ExistingPeriodicWorkPolicy.REPLACE, notificationWork);

ra...@google.com <ra...@google.com> #50Jan 9, 2019 08:22PM

If that is the only worker, then you are good. If there are other workers with other tags involved then using cancelAllWork() is what I would recommend.
Just to ensure that you are starting from a clean slate I would also try and call

https://developer.android.com/reference/android/app/job/JobScheduler#cancelAll(), and reschedule work.

ad...@gmail.com <ad...@gmail.com> #51Feb 3, 2019 01:59PM

Yes, this is the only worker. In the latest build I've added the cancelAllWork() call just to be sure that all work is cancelled (even we don't have more workers), but since we had a lot of crashes, I wasn't allowed to "play" anymore with WorkManager and we replaced it with JobScheduler for API23+ devices.

ad...@gmail.com <ad...@gmail.com> #52May 30, 2019 09:48AM

Hello,

We recently launched an update that includes "androidx.work:work-runtime:2.0.1", and we used it to schedule all our tasks now, in a satisfactory way. I just want to inform, (as you can see in the images attached below), that this problem keeps happening sporadically.

Keep in mind that the number of users affected in our case is small, since the app has several million active users, but it also starts to be worrisome, since the number of errors generated by each user is high.

The errors mainly occur in Android 6 and 7, and sometimes in 8, but especially in Android 7.

I do not expose implementation details, since the documentation of this SDK has been thoroughly studied, and in case there was a bad implementation, the number of errors would be infinitely greater.

Greetings.

workmanager_issue_01.png

37 KB

View

Download

workmanager_issue_02.png

52 KB

View

Download

workmanager_issue_03.png

150 KB

View

Download

[Deleted User] <[Deleted User]> #53May 30, 2019 11:21AM

We are having the same issue as in #52, (lots of crashes from small number of users) on WorkManager 1.0.1

ra...@google.com <ra...@google.com> #54May 30, 2019 05:04PM

Can you please add your notes to this bug report going forward.

https://issuetracker.google.com/issues/134058261

This bug report talks about this crash in the 1.x alpha era. So I just want to disambiguate the problem.

nf...@gmail.com <nf...@gmail.com> #55Sep 9, 2019 09:12AM

Updated workmanager from 1.0.0-beta02 to 1.0.1, as you recommended before, this should fix an issue.
Total crash count is raised drasticly, here we have stats for 40000 devices with 1.0.1 workmanager version: This issue has 46707 crashes affecting 347 users

su...@google.com <su...@google.com> #56Sep 9, 2019 05:05PM

Hi, unfortunately you're dealing with ~6 month old versions at this point. You should upgrade to the latest version (2.2) - we won't be diagnosing issues on older versions anymore.

na...@mercadolibre.com <na...@mercadolibre.com> #57Sep 26, 2019 02:49PM

Hi, we're facing this issue too, also with v1.0.1.

We're using WorkManager#enqueue(OneTimeWorkRequest), instead of WorkManager#beginUniqueWork(OneTimeWorkRequest).

Upgrading to v2.x as you suggest forces us to migrate to Android X too. On v2.x I didn't see anything related in the changelog to justify the migration to Android X.. how can I be sure that migrating both Android X and work-runtime v2.x is gonna fix our issues?

Currently it's happening only in Android 7 (API 24), mainly in Motorola phones (70% Moto C Plus:

https://www.gsmarena.com/motorola_moto_c_plus-8646.php)..

Thank you, regards!

ra...@google.com <ra...@google.com> #58Sep 26, 2019 04:41PM

We made a lot of improvements in 2.X apart from the AndroidX migrations. This problem should go away when you switch to WorkManager 2.2.0. We recommend updating to the latest version asap.

da...@gmail.com <da...@gmail.com> #59Feb 18, 2020 10:44AM

This is a bug.

ju...@gmail.com <ju...@gmail.com> #60Aug 20, 2020 11:54AM

the same problem continues to appear in androidx.work:work-runtime:2.0.1

ra...@gmail.com <ra...@gmail.com> #61Jan 28, 2022 10:34AM

androidx.work:work-runtime-ktx 2.5.0

Fatal Exception: java.lang.IllegalStateException
JobScheduler 100 job limit exceeded. We count 0 WorkManager jobs in JobScheduler; we have 1 tracked jobs in our DB; our Configuration limit is 20.
androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal (SystemJobScheduler.java:204)
androidx.work.impl.background.systemjob.SystemJobScheduler.schedule (SystemJobScheduler.java:132)
androidx.work.impl.Schedulers.schedule (Schedulers.java:108)
androidx.work.impl.utils.ForceStopRunnable.forceStopRunnable (ForceStopRunnable.java:176)
androidx.work.impl.utils.ForceStopRunnable.run (ForceStopRunnable.java:102)
androidx.work.impl.utils.SerialExecutor$Task.run (SerialExecutor.java:91)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
java.lang.Thread.run (Thread.java:764)
Caused by java.lang.IllegalStateException
Apps may not schedule more than 100 distinct jobs
android.os.Parcel.createException (Parcel.java:1958)
android.os.Parcel.readException (Parcel.java:1918)
android.os.Parcel.readException (Parcel.java:1868)
android.app.job.IJobScheduler$Stub$Proxy.schedule (IJobScheduler.java:184)
android.app.JobSchedulerImpl.schedule (JobSchedulerImpl.java:44)
androidx.work.impl.background.systemjob.SystemJobScheduler.scheduleInternal (SystemJobScheduler.java:186)
androidx.work.impl.background.systemjob.SystemJobScheduler.schedule (SystemJobScheduler.java:132)
androidx.work.impl.Schedulers.schedule (Schedulers.java:108)
androidx.work.impl.utils.ForceStopRunnable.forceStopRunnable (ForceStopRunnable.java:176)
androidx.work.impl.utils.ForceStopRunnable.run (ForceStopRunnable.java:102)
androidx.work.impl.utils.SerialExecutor$Task.run (SerialExecutor.java:91)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1167)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:641)
java.lang.Thread.run (Thread.java:764)

ra...@google.com <ra...@google.com> #62Jan 28, 2022 08:06PM

JobScheduler 100 job limit exceeded. We count 0 WorkManager jobs in JobScheduler; we have 1 tracked jobs in our DB; our Configuration limit is 20.

You have other libraries in your app scheduling jobs. This is not WorkManager's fault.

kr...@gmail.com <kr...@gmail.com> #63Sep 8, 2022 11:19AM

In my Samsung Galaxy M30S which recently crashed when checking the rescue log found the same code which is mentioned under more than 100 distinct jobs..... Unfortunately all Samsung service centres asked me to erase 64 GB data and reset phone to resolve. Is there no other solution for the same ?

ap...@gmail.com <ap...@gmail.com> #64Oct 24, 2022 12:21PM

implementation "androidx.work:work-runtime-ktx:2.7.1"

Fatal Exception: java.lang.IllegalStateException JobScheduler 100 job limit exceeded. We count 0 WorkManager jobs in JobScheduler; we have 1 tracked jobs in our DB; our Configuration limit is 20.

Issue 111569265

Description

Issue summary

Comments

hu...@gmail.com <hu...@gmail.com> #2Jul 18, 2018 09:02AM

ra...@google.com <ra...@google.com> #3Jul 18, 2018 04:18PM

hu...@gmail.com <hu...@gmail.com> #4Jul 19, 2018 06:32AM

hu...@gmail.com <hu...@gmail.com> #5Jul 19, 2018 06:33AM

ra...@google.com <ra...@google.com> #6Jul 19, 2018 08:33PM

ra...@google.com <ra...@google.com> #7Jul 19, 2018 09:36PM

hu...@gmail.com <hu...@gmail.com> #8Jul 20, 2018 06:53AM

ra...@google.com <ra...@google.com> Jul 20, 2018 09:29PM

ra...@google.com <ra...@google.com> #9Jul 23, 2018 09:34PM

su...@google.com <su...@google.com> #10Jul 23, 2018 09:47PM

hu...@gmail.com <hu...@gmail.com> #11Jul 24, 2018 08:01PM

hu...@gmail.com <hu...@gmail.com> #12Jul 25, 2018 09:18PM

su...@google.com <su...@google.com> Jul 25, 2018 09:58PM

su...@google.com <su...@google.com> #13Jul 30, 2018 06:08PM

hu...@gmail.com <hu...@gmail.com> #14Jul 31, 2018 08:58AM

hu...@gmail.com <hu...@gmail.com> #15Aug 1, 2018 08:08AM

su...@google.com <su...@google.com> #16Aug 1, 2018 06:18PM

hu...@gmail.com <hu...@gmail.com> #17Aug 2, 2018 10:49AM

hu...@gmail.com <hu...@gmail.com> #18Aug 2, 2018 10:50AM

ra...@google.com <ra...@google.com> #19Aug 2, 2018 10:38PM

hu...@gmail.com <hu...@gmail.com> #20Aug 3, 2018 09:59AM

hu...@gmail.com <hu...@gmail.com> #21Aug 3, 2018 10:07AM

ra...@google.com <ra...@google.com> Aug 3, 2018 10:33PM

ne...@gmail.com <ne...@gmail.com> #22Aug 7, 2018 10:20AM

su...@google.com <su...@google.com> #23Aug 7, 2018 04:23PM

ra...@google.com <ra...@google.com> #24Aug 8, 2018 10:10PM

ra...@google.com <ra...@google.com> #25Aug 8, 2018 10:11PM

al...@gmail.com <al...@gmail.com> #26Aug 28, 2018 08:56AM

jo...@gmail.com <jo...@gmail.com> #27Aug 28, 2018 11:28PM

su...@google.com <su...@google.com> #28Aug 29, 2018 04:01PM

al...@gmail.com <al...@gmail.com> #29Aug 31, 2018 11:54AM

ra...@google.com <ra...@google.com> #30Aug 31, 2018 05:49PM

[Deleted User] <[Deleted User]> #31Sep 3, 2018 06:54AM

mi...@sesma.eu <mi...@sesma.eu> #32Sep 6, 2018 11:07AM

su...@google.com <su...@google.com> #33Sep 6, 2018 04:28PM

al...@gmail.com <al...@gmail.com> #34Sep 12, 2018 06:37AM

[Deleted User] <[Deleted User]> #35Sep 19, 2018 02:23PM

ra...@google.com <ra...@google.com> #36Sep 19, 2018 04:18PM

cr...@supercomputo.mx <cr...@supercomputo.mx> #37Sep 29, 2018 08:38PM

te...@gmail.com <te...@gmail.com> #38Oct 22, 2018 09:10AM

te...@gmail.com <te...@gmail.com> #39Oct 22, 2018 09:17AM

mi...@sesma.eu <mi...@sesma.eu> #40Oct 22, 2018 09:30AM

te...@gmail.com <te...@gmail.com> #41Oct 22, 2018 09:33AM

so...@gmail.com <so...@gmail.com> #42Oct 26, 2018 10:05PM

ad...@gmail.com <ad...@gmail.com> #43Dec 19, 2018 08:38AM

ra...@google.com <ra...@google.com> #44Dec 19, 2018 06:11PM

ad...@gmail.com <ad...@gmail.com> #45Dec 20, 2018 09:33PM

ra...@google.com <ra...@google.com> #46Dec 20, 2018 10:05PM

ad...@gmail.com <ad...@gmail.com> #47Jan 8, 2019 08:38PM

ra...@google.com <ra...@google.com> #48Jan 9, 2019 12:21AM

ad...@gmail.com <ad...@gmail.com> #49Jan 9, 2019 06:58PM

ra...@google.com <ra...@google.com> #50Jan 9, 2019 08:22PM

ad...@gmail.com <ad...@gmail.com> #51Feb 3, 2019 01:59PM

ad...@gmail.com <ad...@gmail.com> #52May 30, 2019 09:48AM

[Deleted User] <[Deleted User]> #53May 30, 2019 11:21AM

ra...@google.com <ra...@google.com> #54May 30, 2019 05:04PM

nf...@gmail.com <nf...@gmail.com> #55Sep 9, 2019 09:12AM

su...@google.com <su...@google.com> #56Sep 9, 2019 05:05PM

na...@mercadolibre.com <na...@mercadolibre.com> #57Sep 26, 2019 02:49PM

ra...@google.com <ra...@google.com> #58Sep 26, 2019 04:41PM

da...@gmail.com <da...@gmail.com> #59Feb 18, 2020 10:44AM

ju...@gmail.com <ju...@gmail.com> #60Aug 20, 2020 11:54AM

ra...@gmail.com <ra...@gmail.com> #61Jan 28, 2022 10:34AM

ra...@google.com <ra...@google.com> #62Jan 28, 2022 08:06PM

kr...@gmail.com <kr...@gmail.com> #63Sep 8, 2022 11:19AM

ap...@gmail.com <ap...@gmail.com> #64Oct 24, 2022 12:21PM

Add comment

Issue metadata