IssueTracker

Project: chromiumos/overlays/chromiumos-overlay
Branch: main

commit d9fcf3ac6751e611ab8a1970310ac6e7bf01f463
Author: Alec Bargher <abargher@google.com>
Date:   Wed Aug 21 15:51:24 2024

    dev-util: Add workaround for armv7a boards compiling LLDB
   
    Currently armv7a is not parsed as a supported architecture by LLDB.
    Compiling with the host architecture in the triple set to "arm" instead
    of "armv7a" can work around this issue before LLDB itself is patched.
   
    BUG=b:361414339
    TEST=USE="local-lldb" cros build-packages --board=${BOARD}
   
    Change-Id: I7c18ab9354b09fd91ac3635a8bcb4ac177f0d3cd
    Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/5805607
    Reviewed-by: Jordan Abrahams-Whitehead <ajordanr@google.com>
    Commit-Queue: Alec Bargher <abargher@google.com>
    Tested-by: Alec Bargher <abargher@google.com>
    Commit-Queue: ChromeOS Auto Runner <chromeos-auto-runner@chromeos-bot.iam.gserviceaccount.com>

M       dev-util/lldb-server/lldb-server-9999.ebuild

https://chromium-review.googlesource.com/5805607

Project: chromiumos/overlays/chromiumos-overlay
Branch: main

commit a19a091eb14534ec05e14447677665111a635eaf
Author: Jordan R Abrahams-Whitehead <ajordanr@google.com>
Date:   Thu Aug 29 19:20:50 2024

    llvm: Downstream armv7a, armv8a patch
   
    armv7a and armv8a are common names for the application subarch for arm.
   
    These names in particular are used in ChromeOS, Android, and a few other
    known applications. In ChromeOS, we encountered a bug where armv7a arch
    was not recognised and segfaulted when starting an executable on an
    arm32 device.
   
    Recreating this cl:
    get_patch.py -s HEAD 0a00d32c5f88fce89006dcde6e235bc77d7b495e
   
    BUG=b:361414339
    TEST=Ran with lldb-hana under qemu-arm
   
    Change-Id: I5af0f832bb657780232b59d8014133a25581ea2f
    Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/5827378
    Tested-by: Jordan Abrahams-Whitehead <ajordanr@google.com>
    Reviewed-by: Bob Haarman <inglorion@chromium.org>
    Commit-Queue: Jordan Abrahams-Whitehead <ajordanr@google.com>

A       dev-util/lldb-server/files/0a00d32c5f88fce89006dcde6e235bc77d7b495e.patch
M       dev-util/lldb-server/files/PATCHES.json
M       sys-devel/llvm/files/PATCHES.json
A       sys-devel/llvm/files/cherry/0a00d32c5f88fce89006dcde6e235bc77d7b495e.patch

https://chromium-review.googlesource.com/5827378

Project: chromiumos/overlays/chromiumos-overlay
Branch: firmware-android-15949.B

commit ead6651016c1015b4771244b390ab72630b9dea9
Author: Alec Bargher <abargher@google.com>
Date:   Wed Aug 21 15:51:24 2024

    dev-util: Add workaround for armv7a boards compiling LLDB
   
    Currently armv7a is not parsed as a supported architecture by LLDB.
    Compiling with the host architecture in the triple set to "arm" instead
    of "armv7a" can work around this issue before LLDB itself is patched.
   
    BUG=b:361414339
    TEST=USE="local-lldb" cros build-packages --board=${BOARD}
   
    (cherry picked from commit d9fcf3ac6751e611ab8a1970310ac6e7bf01f463)
   
    Change-Id: I7c18ab9354b09fd91ac3635a8bcb4ac177f0d3cd
    Original-Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/5805607
    Original-Reviewed-by: Jordan Abrahams-Whitehead <ajordanr@google.com>
    Original-Commit-Queue: Alec Bargher <abargher@google.com>
    Original-Tested-by: Alec Bargher <abargher@google.com>
    Original-Commit-Queue: ChromeOS Auto Runner <chromeos-auto-runner@chromeos-bot.iam.gserviceaccount.com>
    GitOrigin-RevId: d9fcf3ac6751e611ab8a1970310ac6e7bf01f463
    Cr-Build-Id: 8735988028124072689
    Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8735988028124072689
    Copybot-Job-Name: android-main-chromiumos-overlay-copybot-downstream
    Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/5885433
    Reviewed-by: Grzegorz Bernacki <bernacki@google.com>
    Owners-Override: Aaron Massey <aaronmassey@google.com>
    Tested-by: Jonathon Murphy <jpmurphy@google.com>

M       dev-util/lldb-server/lldb-server-9999.ebuild

https://chromium-review.googlesource.com/5885433

Project: chromiumos/overlays/chromiumos-overlay
Branch: firmware-android-15949.B

commit 6bbde850cd778c4048a3e4b9cb445bc0442b87c6
Author: Jordan R Abrahams-Whitehead <ajordanr@google.com>
Date:   Thu Aug 29 19:20:50 2024

    llvm: Downstream armv7a, armv8a patch
   
    armv7a and armv8a are common names for the application subarch for arm.
   
    These names in particular are used in ChromeOS, Android, and a few other
    known applications. In ChromeOS, we encountered a bug where armv7a arch
    was not recognised and segfaulted when starting an executable on an
    arm32 device.
   
    Recreating this cl:
    get_patch.py -s HEAD 0a00d32c5f88fce89006dcde6e235bc77d7b495e
   
    BUG=b:361414339
    TEST=Ran with lldb-hana under qemu-arm
   
    (cherry picked from commit a19a091eb14534ec05e14447677665111a635eaf)
   
    Change-Id: I5af0f832bb657780232b59d8014133a25581ea2f
    Original-Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/5827378
    Original-Tested-by: Jordan Abrahams-Whitehead <ajordanr@google.com>
    Original-Reviewed-by: Bob Haarman <inglorion@chromium.org>
    Original-Commit-Queue: Jordan Abrahams-Whitehead <ajordanr@google.com>
    GitOrigin-RevId: a19a091eb14534ec05e14447677665111a635eaf
    Cr-Build-Id: 8735988028124072689
    Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8735988028124072689
    Copybot-Job-Name: android-main-chromiumos-overlay-copybot-downstream
    Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/5885669
    Reviewed-by: Grzegorz Bernacki <bernacki@google.com>
    Owners-Override: Aaron Massey <aaronmassey@google.com>
    Tested-by: Jonathon Murphy <jpmurphy@google.com>

A       dev-util/lldb-server/files/0a00d32c5f88fce89006dcde6e235bc77d7b495e.patch
M       dev-util/lldb-server/files/PATCHES.json
M       sys-devel/llvm/files/PATCHES.json
A       sys-devel/llvm/files/cherry/0a00d32c5f88fce89006dcde6e235bc77d7b495e.patch

https://chromium-review.googlesource.com/5885669

Hi. I've received your bug and will wait until https://chromium-review.googlesource.com/5908479 is merged and then change assignee to ajordanr@google.com and mark as fixed.

We have gone back to 2.0.0 and haven't been able to make it crash again unfortunately. Will keep trying. We are rolling out an update next week that reverts to 1.0.0 and will let you know if the crash goes away in production as well

I just want to distinguish between which versions you are using/experiencing this on.

1. The bug title lists 2.0.0
2. The first update lists 2.0.1-rc01
3. #14 lists 2.0.0

Can you reproduce at all with any version of WorkManager 2.x at this point?  And if so, which ones work and which ones don't?

Our store version had 2.0.0 and is what the screenshots come from, we reproduced locally using that. We upgraded to 2.0.1rc1 and the phone was still crashing. We downgraded to 1.0.0 and the crash went away. To help with this testing we went back to 2.0.0 to try and get it to crash again but we haven't been able to get it to happen again.

We rolled out an update to the Play Store using WorkManager 1.0.0 and the issue has persisted unfortunately

Not sure it helps but this trace has a few more lines in it.

backtrace:
  #00  pc 0000000000000000  <unknown>
  #01  pc 0000000000025cdd  /system/lib/libsqlite.so
  #02  pc 0000000000025011  /system/lib/libsqlite.so
  #03  pc 000000000000eb95  /system/lib/libsqlite.so
  #04  pc 000000000002d60d  /system/lib/libsqlite.so
  #05  pc 000000000003b409  /system/lib/libsqlite.so
  #06  pc 0000000000010931  /system/lib/libsqlite.so (sqlite3_step+536)
  #07  pc 000000000007f175  /system/lib/libandroid_runtime.so
  #08  pc 00000000018a0a33  /system/framework/arm/boot-framework.oat (android.database.sqlite.SQLiteConnection.nativeExecute+102)
  #09  pc 00000000018a34b9  /system/framework/arm/boot-framework.oat (android.database.sqlite.SQLiteConnection.execute+260)
  #10  pc 00000000018b3741  /system/framework/arm/boot-framework.oat (android.database.sqlite.SQLiteSession.endTransactionUnchecked+364)
  #11  pc 00000000018b3ee5  /system/framework/arm/boot-framework.oat (android.database.sqlite.SQLiteSession.endTransaction+144)
  #12  pc 00000000018ac61d  /system/framework/arm/boot-framework.oat (android.database.sqlite.SQLiteDatabase.endTransaction+72)
  #13  pc 00000000000a91c1  /system/lib/libart.so (art_quick_invoke_stub_internal+64)
  #14  pc 00000000004031e9  /system/lib/libart.so (art_quick_invoke_stub+232)
  #15  pc 00000000000b0455  /system/lib/libart.so (_ZN3art9ArtMethod6InvokeEPNS_6ThreadEPjjPNS_6JValueEPKc+136)
  #16  pc 00000000001ec389  /system/lib/libart.so (_ZN3art11interpreter34ArtInterpreterToCompiledCodeBridgeEPNS_6ThreadEPNS_9ArtMethodEPKNS_7DexFile8CodeItemEPNS_11ShadowFrameEPNS_6JValueE+200)
  #17  pc 00000000001e6939  /system/lib/libart.so (_ZN3art11interpreter6DoCallILb0ELb0EEEbPNS_9ArtMethodEPNS_6ThreadERNS_11ShadowFrameEPKNS_11InstructionEtPNS_6JValueE+492)
  #18  pc 00000000003fd663  /system/lib/libart.so (MterpInvokeVirtualQuick+322)
  #19  pc 000000000009fd94  /system/lib/libart.so (ExecuteMterpImpl+29972)
  #20  pc 00000000001ca783  /system/lib/libart.so (_ZN3art11interpreterL7ExecuteEPNS_6ThreadEPKNS_7DexFile8CodeItemERNS_11ShadowFrameENS_6JValueEb+290)
  #21  pc 00000000001cf2eb  /system/lib/libart.so (_ZN3art11interpreter33ArtInterpreterToInterpreterBridgeEPNS_6ThreadEPKNS_7DexFile8CodeItemEPNS_11ShadowFrameEPNS_6JValueE+114)
  #22  pc 00000000001e691f  /system/lib/libart.so (_ZN3art11interpreter6DoCallILb0ELb0EEEbPNS_9ArtMethodEPNS_6ThreadERNS_11ShadowFrameEPKNS_11InstructionEtPNS_6JValueE+466)
  #23  pc 00000000003fb92b  /system/lib/libart.so (MterpInvokeInterface+826)
  #24  pc 000000000009c214  /system/lib/libart.so (ExecuteMterpImpl+14740)
  #25  pc 00000000001ca783  /system/lib/libart.so (_ZN3art11interpreterL7ExecuteEPNS_6ThreadEPKNS_7DexFile8CodeItemERNS_11ShadowFrameENS_6JValueEb+290)
  #26  pc 00000000001cf2eb  /system/lib/libart.so (_ZN3art11interpreter33ArtInterpreterToInterpreterBridgeEPNS_6ThreadEPKNS_7DexFile8CodeItemEPNS_11ShadowFrameEPNS_6JValueE+114)
  #27  pc 00000000001e691f  /system/lib/libart.so (_ZN3art11interpreter6DoCallILb0ELb0EEEbPNS_9ArtMethodEPNS_6ThreadERNS_11ShadowFrameEPKNS_11InstructionEtPNS_6JValueE+466)
  #28  pc 00000000003fd663  /system/lib/libart.so (MterpInvokeVirtualQuick+322)
  #29  pc 000000000009fd94  /system/lib/libart.so (ExecuteMterpImpl+29972)
  #30  pc 00000000001ca783  /system/lib/libart.so (_ZN3art11interpreterL7ExecuteEPNS_6ThreadEPKNS_7DexFile8CodeItemERNS_11ShadowFrameENS_6JValueEb+290)
  #31  pc 00000000001cf255  /system/lib/libart.so (_ZN3art11interpreter30EnterInterpreterFromEntryPointEPNS_6ThreadEPKNS_7DexFile8CodeItemEPNS_11ShadowFrameE+92)
  #32  pc 00000000003f269f  /system/lib/libart.so (artQuickToInterpreterBridge+706)
  #33  pc 00000000000adc13  /system/lib/libart.so (art_quick_to_interpreter_bridge+34)
  #34  pc 000000000064b125  /system/framework/arm/boot-core-libart.oat (java.util.concurrent.ThreadPoolExecutor.runWorker+344)
  #35  pc 0000000000652b47  /system/framework/arm/boot-core-libart.oat (java.util.concurrent.ThreadPoolExecutor$Worker.run+42)
  #36  pc 00000000005f749d  /system/framework/arm/boot.oat (java.lang.Thread.run+48)
  #37  pc 00000000000a91c1  /system/lib/libart.so (art_quick_invoke_stub_internal+64)
  #38  pc 00000000004031e9  /system/lib/libart.so (art_quick_invoke_stub+232)
  #39  pc 00000000000b0455  /system/lib/libart.so (_ZN3art9ArtMethod6InvokeEPNS_6ThreadEPjjPNS_6JValueEPKc+136)
  #40  pc 0000000000314031  /system/lib/libart.so (_ZN3artL18InvokeWithArgArrayERKNS_33ScopedObjectAccessAlreadyRunnableEPNS_9ArtMethodEPNS_8ArgArrayEPNS_6JValueEPKc+56)
  #41  pc 0000000000314dfd  /system/lib/libart.so (_ZN3art35InvokeVirtualOrInterfaceWithJValuesERKNS_33ScopedObjectAccessAlreadyRunnableEP8_jobjectP10_jmethodIDP6jvalue+256)
  #42  pc 000000000032be19  /system/lib/libart.so (_ZN3art6Thread14CreateCallbackEPv+848)
  #43  pc 0000000000046eb3  /system/lib/libc.so (_ZL15__pthread_startPv+22)
  #44  pc 0000000000019acd  /system/lib/libc.so (__start_thread+6)

Unfortunately, this is still not telling us anything we can diagnose.  Paired with the fact that we haven't gotten any other reports of this issue, it's not clear how we should proceed.  We would need Motorola system images to proceed at this point.  I can suggest one more thing: if you go back to the last version that worked fine for you and simply change your WorkManager dependency (but *not* any of the rest of your app's code changes), does it immediately exhibit the crash?  Basically, I'm wondering if something else with your code is triggering or exacerbating the issue.

Ping to the original reporter(s).

Sorry I have been on leave for Easter. I think you are right about some other code change triggering this bug, will see if I can work anything out. I am at I/O next week as well if you want to have a look yourself.

Thanks, closing this out for now - feel free to reply if there's anything else we can assist you with on this matter.

This is a definite stab in the dark but do you use a ForeignKey with Room? This is the only reference I can find to similar crashes online. https://stackoverflow.com/questions/50662521/tombstone-using-foreignkey-with-room

We do use foreign keys, but we've been doing that since our early alpha versions so I'm not sure that's it.

Fair enough, both crash reports have this sqlite3_step+536 in common. Will keep trying to work it out.

We seem to have narrowed this down to calling

WorkManager.initialize(applicationContext, workManagerConfig)
WorkManager.getInstance().getWorkInfosByTagLiveData(DownloadManager.WORK_MANAGER_DOWNLOAD_TAG).observeForever {}

If we wrap the second line in a coroutine to main just to delay it a cycle then the crash goes away, at least on our test device. We might roll out the fix to test it.

Hi, I'm glad you have some reproducible steps.  It would help us a lot if you could actually boil this down to a minimal sample app that can reproduce it so you can share it with us and we can also examine what is going wrong.

Done! This crashes for us on the second launch, you need a large amount queued jobs for it to happen. Testing on a Moto X 2014 victara running Android 6.0.

We managed to get a test device, and I can reproduce it.

I see this:

05-21 10:18:50.804   352   352 D SFPerfTracer:        layers: (6:13) (FocusedStackFrame (0xb8370eb8): 0:108)* (DimLayer (0xb83412c0): 9:12) (StatusBar (0xb83bbf38): 0:701) (NavigationBar (0xb8389d10): 0:550) (com.android.systemui.ImageWallpaper (0xb83b23f8): 0:234) (DimLayer (0xb83989f0): 0:45)- (DimLayer (0xb83907e0): 0:8)- (com.example.workmanagercrash/com.example.workmanagercrash.MainActivity (0xb836c948): 0:31)- (com.android.systemui/com.android.systemui.recents.RecentsActivity (0xb838d188): 0:58)- (thumbnail anim (0xb834e7a0): 0:23)- (com.google.android.googlequicksearchbox/com.google.android.launcher.GEL (0xb834e7a0): 0:13) (Application Error: com.example.workmanagercrash (0xb83989f0): 8:14)
05-21 10:18:50.804   463   463 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-21 10:18:50.804   463   463 F DEBUG   : Build fingerprint: 'motorola/victara_tmo/victara:6.0/MPES24.49-18-7/7:user/release-keys'
05-21 10:18:50.805   463   463 F DEBUG   : Revision: 'p2bf'
05-21 10:18:50.805   463   463 F DEBUG   : ABI: 'arm'
05-21 10:18:50.805   463   463 F DEBUG   : pid: 9165, tid: 9180, name: WorkManager-Wor  >>> com.example.workmanagercrash <<<
05-21 10:18:50.805   463   463 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
05-21 10:18:50.819   463   463 F DEBUG   :     r0 b9b04660  r1 af9ece50  r2 00000000  r3 00000002
05-21 10:18:50.819   463   463 F DEBUG   :     r4 b9b044b8  r5 b692e118  r6 00000000  r7 b9b04f08
05-21 10:18:50.819   463   463 F DEBUG   :     r8 00000001  r9 b9b044b8  sl 00000000  fp 00000002
05-21 10:18:50.819   463   463 F DEBUG   :     ip b692ddfc  sp af9ece28  lr b6881e5b  pc 00000000  cpsr 200f0010
05-21 10:18:50.823   463   463 F DEBUG   :
05-21 10:18:50.823   463   463 F DEBUG   : backtrace:
05-21 10:18:50.824   463   463 F DEBUG   :     #00 pc 00000000  <unknown>
05-21 10:18:50.824   463   463 F DEBUG   :     #01 pc 00024e59  /system/lib/libsqlite.so
05-21 10:18:50.824   463   463 F DEBUG   :     #02 pc 00024173  /system/lib/libsqlite.so
05-21 10:18:50.824   463   463 F DEBUG   :     #03 pc 0000e759  /system/lib/libsqlite.so
05-21 10:18:50.824   463   463 F DEBUG   :     #04 pc 0002be41  /system/lib/libsqlite.so
05-21 10:18:50.824   463   463 F DEBUG   :     #05 pc 00039ad7  /system/lib/libsqlite.so
05-21 10:18:50.824   463   463 F DEBUG   :     #06 pc 0000ffc5  /system/lib/libsqlite.so (sqlite3_step+724)
05-21 10:18:50.824   463   463 F DEBUG   :     #07 pc 00075021  /system/lib/libandroid_runtime.so
05-21 10:18:50.824   463   463 F DEBUG   :     #08 pc 02287663  /system/framework/arm/boot.oat (offset 0x1fda000)
05-21 10:18:51.062  1769  2069 V AlarmManager: sending alarm {f6ba791 type 3 *alarm*:android.content.jobscheduler.JOB_DELAY_EXPIRED}
05-21 10:18:51.065  1769  1769 V AlarmManager: done {f6ba791, *alarm*:android.content.jobscheduler.JOB_DELAY_EXPIRED} [3ms]
05-21 10:18:51.131   463   463 F DEBUG   :
05-21 10:18:51.131   463   463 F DEBUG   : Tombstone written to: /data/tombstones/tombstone_01
05-21 10:18:51.131   463   463 E DEBUG   : AM write failed: Broken pipe
05-21 10:18:51.133  1769  1786 I BootReceiver: Copying /data/tombstones/tombstone_01 to DropBox (SYSTEM_TOMBSTONE)
05-21 10:18:51.184   485   485 I Zygote  : Process 9165 exited due to signal (11)
05-21 10:18:51.214  1769  2729 I ActivityManager: Process com.example.workmanagercrash (pid 9165) has died
05-21 10:18:51.215  1769  2729 W ActivityManager: Scheduling restart of crashed service com.example.workmanagercrash/androidx.work.impl.background.systemjob.SystemJobService in 1000ms
05-21 10:18:51.238  1769  1769 I ActivityManager: Start proc 9188:com.example.workmanagercrash/u0a106 for service com.example.workmanagercrash/androidx.work.impl.background.systemjob.SystemJobService
05-21 10:18:51.256  9188  9188 I art     : Late-enabling -Xcheck:jni
05-21 10:18:51.301  9188  9188 W System  : ClassLoader referenced unknown path: /data/app/com.example.workmanagercrash-1/lib/arm
05-21 10:18:51.476  9188  9202 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 9202 (WorkManager-Wor)
05-21 10:18:51.578   463   463 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-21 10:18:51.578   463   463 F DEBUG   : Build fingerprint: 'motorola/victara_tmo/victara:6.0/MPES24.49-18-7/7:user/release-keys'
05-21 10:18:51.579   463   463 F DEBUG   : Revision: 'p2bf'
05-21 10:18:51.579   463   463 F DEBUG   : ABI: 'arm'
05-21 10:18:51.579   463   463 F DEBUG   : pid: 9188, tid: 9202, name: WorkManager-Wor  >>> com.example.workmanagercrash <<<
05-21 10:18:51.580   463   463 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
05-21 10:18:51.609   463   463 F DEBUG   :     r0 b9b048c0  r1 af9ece50  r2 00000000  r3 00000002
05-21 10:18:51.609   463   463 F DEBUG   :     r4 b9b04718  r5 b692e118  r6 00000000  r7 b9b05170
05-21 10:18:51.609   463   463 F DEBUG   :     r8 00000001  r9 b9b04718  sl 00000000  fp 00000002
05-21 10:18:51.609   463   463 F DEBUG   :     ip b692ddfc  sp af9ece28  lr b6881e5b  pc 00000000  cpsr 200f0010
05-21 10:18:51.615   463   463 F DEBUG   :
05-21 10:18:51.615   463   463 F DEBUG   : backtrace:
05-21 10:18:51.616   463   463 F DEBUG   :     #00 pc 00000000  <unknown>
05-21 10:18:51.616   463   463 F DEBUG   :     #01 pc 00024e59  /system/lib/libsqlite.so
05-21 10:18:51.616   463   463 F DEBUG   :     #02 pc 00024173  /system/lib/libsqlite.so
05-21 10:18:51.616   463   463 F DEBUG   :     #03 pc 0000e759  /system/lib/libsqlite.so
05-21 10:18:51.616   463   463 F DEBUG   :     #04 pc 0002be41  /system/lib/libsqlite.so
05-21 10:18:51.616   463   463 F DEBUG   :     #05 pc 00039ad7  /system/lib/libsqlite.so
05-21 10:18:51.616   463   463 F DEBUG   :     #06 pc 0000ffc5  /system/lib/libsqlite.so (sqlite3_step+724)
05-21 10:18:51.616   463   463 F DEBUG   :     #07 pc 00075021  /system/lib/libandroid_runtime.so
05-21 10:18:51.616   463   463 F DEBUG   :     #08 pc 02287663  /system/framework/arm/boot.oat (offset 0x1fda000)
05-21 10:18:51.902   463   463 F DEBUG   :
05-21 10:18:51.902   463   463 F DEBUG   : Tombstone written to: /data/tombstones/tombstone_02
05-21 10:18:51.902   463   463 E DEBUG   : AM write failed: Broken pipe
05-21 10:18:51.903  1769  1786 I BootReceiver: Copying /data/tombstones/tombstone_02 to DropBox (SYSTEM_TOMBSTONE)
05-21 10:18:51.952   485   485 I Zygote  : Process 9188 exited due to signal (11)
05-21 10:18:51.966  1769  2757 I ActivityManager: Process com.example.workmanagercrash (pid 9188) has died

Project: platform/frameworks/support
Branch: androidx-master-dev

commit 957adb282e41c2662fff6221325e6b51cd7377f9
Author: Rahul Ravikumar <rahulrav@google.com>
Date:   Tue May 21 14:37:00 2019

    Fixes SQLite issues on some devices.
   
    * Always beginTransaction() outside a try.
    * Make sure SystemJobScheduler marks transactions as successful.
   
    Test: Existing tests pass.
    Fixes: b/130182503, b/132697495
    Change-Id: I55092537781fbfee97f4336eb7cf1a49e647d62a

M       work/workmanager-gcm/src/main/java/androidx/work/impl/background/gcm/WorkManagerGcmDispatcher.java
M       work/workmanager/src/main/java/androidx/work/impl/WorkerWrapper.java
M       work/workmanager/src/main/java/androidx/work/impl/background/systemjob/SystemJobScheduler.java
M       work/workmanager/src/main/java/androidx/work/impl/utils/ForceStopRunnable.java

https://android-review.googlesource.com/966057
https://goto.google.com/android-sha1/957adb282e41c2662fff6221325e6b51cd7377f9

Will it be fixed in a maintainance release of 2.0, or will we have to wait for 2.1 next RC or release?

This will show up in the next 2.1.0 release.