Status Update
Comments
da...@google.com <da...@google.com> #2
I'm not sure how to edit the description. But forgot to add that this will work when the app is in the foreground. It just doesn't work when you lock your device. I test this by moving the app to the background and then locking my device and checking the logs in Android Studio.
ra...@google.com <ra...@google.com> #3
It would be great if you could prioritize a fix for this issue. Additionally, if there are any alternative ways we can address this from our side, please let us know. Thank you!
li...@samsung.corp-partner.google.com <li...@samsung.corp-partner.google.com> #4
We also experienced issues with the new version 2.10.0. In our app a Job that is launched at start of the app is triggered and then immediatly cancelled because constraints are not meet anymore. I tried everything from putting it as a foreground job removing all constraints on the job but the behavior stay the same. I will rollback to 2.9.1 until it's fixed. You will find attached some logs of the WM in our app, take a look at job fec664f7-e40c-4df1-baca-3cbc7e1b1ff9.
Description
Version used:2.8.1
Devices/Android versions reproduced on:
devices:SM-P620
android versions:14.
description:
We used workManager as the scheduler for video classification in the application, but we found that when the memory is low, workManager will throw an exception and cannot catch it, which causes the app to crash. Can you tell me how to handle this exception gracefully so that the application does not crash even in low memory state?
--------------------
06-21 11:42:40.528 root 581 581 D io_stats: !@ DiskUsage: /data 96.87 % used (47857 MB/ 49402 MB)
06-21 11:42:42.528 root 581 581 D io_stats: !@ DiskUsage: /data 97.11 % used (47979 MB/ 49402 MB)
06-21 11:42:44.532 root 581 581 D io_stats: !@ DiskUsage: /data 97.39 % used (48115 MB/ 49402 MB)
06-21 11:42:46.534 root 581 581 D io_stats: !@ DiskUsage: /data 97.62 % used (48228 MB/ 49402 MB)
06-21 11:42:50.537 root 581 581 D io_stats: !@ DiskUsage: /data 98.21 % used (48521 MB/ 49402 MB)
06-21 11:42:52.539 root 581 581 D io_stats: !@ DiskUsage: /data 98.55 % used (48687 MB/ 49402 MB)
06-21 11:42:54.541 root 581 581 D io_stats: !@ DiskUsage: /data 98.88 % used (48851 MB/ 49402 MB)
06-21 11:42:56.543 root 581 581 D io_stats: !@ DiskUsage: /data 99.23 % used (49025 MB/ 49402 MB)
06-21 11:42:58.544 root 581 581 D io_stats: !@ DiskUsage: /data 99.57 % used (49192 MB/ 49402 MB)
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: FATAL EXCEPTION: WM.task-4
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: Process: com.samsung.android.smartprovider, PID: 25565
----------------------------
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: android.database.sqlite.SQLiteFullException: database or disk is full (code 13 SQLITE_FULL[13])
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: at android.database.sqlite.SQLiteConnection.nativeExecute(Native Method)
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: at android.database.sqlite.SQLiteConnection.execute(SQLiteConnection.java:1033)
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: at android.database.sqlite.SQLiteSession.endTransactionUnchecked(SQLiteSession.java:439)
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: at android.database.sqlite.SQLiteSession.endTransaction(SQLiteSession.java:403)
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: at android.database.sqlite.SQLiteDatabase.endTransaction(SQLiteDatabase.java:990)
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: at l1.b.c(Unknown Source:2)
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: at g1.p.g(Unknown Source:8)
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: at a2.j.run(Unknown Source:108)
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: at androidx.appcompat.widget.k.run(Unknown Source:63)
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
06-21 11:43:18.621 10162 25565 25623 E AndroidRuntime: at java.lang.Thread.run(Thread.java:1012)
If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue.
- A screenrecord or screenshots showing the issue (if UI related).