ANR from RescheduleReceiver with TIME_SET intent [236906724]

Fixed

Bug

Status Update

No update yet.

Description

jp...@samsung.corp-partner.google.com

created issue #1

Jun 23, 2022 03:48AM

Component used: androidx.work:work-runtime:2.7
Version used: 2.7
Devices/Android versions reproduced on: Gallery S22 S OS

Hi. I am a sw engieer and my project is using worker.
I got ANR issue below which comes from RescheduleReceiver.

06-07 10:23:49.655 1000 2195 14874 E ActivityManager: ANR in XXX
06-07 10:23:49.655 1000 2195 14874 E ActivityManager: PID: 12162
06-07 10:23:49.655 1000 2195 14874 E ActivityManager: Reason: Broadcast of Intent { act=android.intent.action.TIME_SET flg=0x25200010 cmp=com.samsung.android.scs/androidx.work.impl.background.systemalarm.RescheduleReceiver }

From my debugging,
worker register static RescheduleReceiver in AndroidManifest.
and this receiver use BroadcastReceiver.goAsync() method.

@Override
public void onReceive(Context context, Intent intent) {
Logger.get().debug(TAG, String.format("Received intent %s", intent));
if (Build.VERSION.SDK_INT >= WorkManagerImpl.MIN_JOB_SCHEDULER_API_LEVEL) {
try {
WorkManagerImpl workManager = WorkManagerImpl.getInstance(context);
final PendingResult pendingResult = goAsync();
workManager.setReschedulePendingResult(pendingResult);

As described developer site,
when you use goAync() method, you must call PendingResult.finish() after work.

https://developer.android.com/reference/android/content/BroadcastReceiver#goAsync()

https://developer.android.com/reference/android/content/BroadcastReceiver.PendingResult#finish()

But in workManager.setReschedulePendingResult(pendingResult);
there is a posibility not to call PendingResult.finish() when ForceStopRunnable is not compeleted.

public void setReschedulePendingResult(
@NonNull BroadcastReceiver.PendingResult rescheduleReceiverResult) {
synchronized (sLock) {
mRescheduleReceiverResult = rescheduleReceiverResult;
if (mForceStopRunnableCompleted) {
mRescheduleReceiverResult.finish();
mRescheduleReceiverResult = null;
}
}
}

This ANR is reproducible only when the process is launched by RescheduleReceiver.
You may can test with these intent.

<action android:name="android.intent.action.BOOT_COMPLETED" />
<action android:name="android.intent.action.TIME_SET" />
<action android:name="android.intent.action.TIMEZONE_CHANGED" />

This is not a hundred percent issue but it's reproducible sometimes as timing issue.

Also Similar issues were already reported before

https://issuetracker.google.com/issues?q=TITLE:%20ANR%20AND%20TIME_SET%20AND%20work
It means there is a problem.

ForceStopRunnable is triggered on background. It cannot guarantee that it's completed when BR handles this intent.
Please check this call stack.
WorkManagerImpl's constructor schedule ForceStopRunnable with executor and return directly.

WorkManagerImp.java
Constructor --> internalInit() --> mWorkTaskExecutor.executeOnBackgroundThread(new ForceStopRunnable(context, this));

And in here RescheduleReceiver .onReceive()
There is no logic to hold until ForceStopRunnable is completed.
This issue is not related to the main looper, it's mWorkTaskExecutor.
If an executor is busy, there is a possibility that ForceStopRunnable is delayed.
When it is delayed, mForceStopRunnableCompleted field can be false and returns onRecieve() with not finishing PendingResult.
Could you please check with this? Thanks

RescheduleReceiver.java
@Override
public void onReceive(Context context, Intent intent) {
...
WorkManagerImpl workManager = WorkManagerImpl.getInstance(context);
final PendingResult pendingResult = goAsync();
workManager.setReschedulePendingResult(pendingResult);
...
}

WorkManagerImp.java
public void setReschedulePendingResult(
@NonNull BroadcastReceiver.PendingResult rescheduleReceiverResult) {
synchronized (sLock) {
mRescheduleReceiverResult = rescheduleReceiverResult;
if (mForceStopRunnableCompleted) {
mRescheduleReceiverResult.finish();
mRescheduleReceiverResult = null;
}
}
}

Comments

se...@google.com <se...@google.com> #2Jun 23, 2022 09:37AM

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?

jp...@samsung.corp-partner.google.com <jp...@samsung.corp-partner.google.com> #3Jun 27, 2022 01:22AM

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

jp...@samsung.corp-partner.google.com <jp...@samsung.corp-partner.google.com> #4Jul 4, 2022 07:57AM

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.

se...@google.com <se...@google.com> #5Jul 6, 2022 10:30AM

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.

jp...@gmail.com <jp...@gmail.com> #6Jul 7, 2022 02:49AM

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)

jp...@gmail.com <jp...@gmail.com> #7Jul 15, 2022 08:59AM

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!

jp...@gmail.com <jp...@gmail.com> #8Jul 21, 2022 08:40AM

Thank you, I'll try it and check.

li...@samsung.corp-partner.google.com <li...@samsung.corp-partner.google.com> #9Nov 7, 2022 08:42AM

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.

se...@google.com <se...@google.com> #10Nov 7, 2022 12:14PM

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

li...@samsung.corp-partner.google.com <li...@samsung.corp-partner.google.com> #11Nov 8, 2022 03:23AM

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

se...@google.com <se...@google.com> #12Nov 17, 2022 10:22PM

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!

ya...@gmail.com <ya...@gmail.com> #13Feb 21, 2023 04:44PM

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)

ya...@gmail.com <ya...@gmail.com> #14Feb 24, 2023 03:08PM

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

li...@gmail.com <li...@gmail.com> #15Feb 27, 2023 01:23AM

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!

ya...@gmail.com <ya...@gmail.com> #16Feb 27, 2023 02:59AM

Added workarounds in Known issues section in public docs.

Message last modified on Feb 27, 2023 03:04AM

android.intent.action.BOOT_COMPLETED ANR 2.png

116 KB

View

Download

deleted

0 B

android.intent.action.TIME_SET ANR 2.png

124 KB

View

Download

android.intent.action.TIME_SET ANR.png

141 KB

View

Download

ya...@gmail.com <ya...@gmail.com> #17Feb 27, 2023 03:01AM

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

android.intent.action.BOOT_COMPLETED ANR.png

130 KB

View

Download

se...@google.com <se...@google.com> #18Mar 1, 2023 02:42PM

But, I do not see such logic in RescheduleReceiver. Am I missing something? I was pondering, if 1st goAsync occur, and then 2nd goAsync occur again before the mRescheduleReceiverResult.finish() associated with 1st goAsync is executed, can 2nd goAsync causes ANR?

We think that it is highly likely that second goAsync triggers ANR. We actually even tried to address it in aosp/2401352. However apps that use nightly build of androidx (you can use it too, see) reported huge spike in volume of ANRs specifically on android T. So that fix was reverted. Once we confirm that ANR goes back to previous number, we'll explore why that CL was triggering more ANRs on T (likely platform bug) and how else we can address ANRs.

ya...@gmail.com <ya...@gmail.com> #19Mar 1, 2023 05:21PM

Hi Googlers,

It isn't clear on why the initial proposed fix (which is now reverted) can cause spike in ANR.

It isn't totally clear too, on why current 2.8.0 WM is causing ANR. Hypothesis provided by Samsung engineer might hold true.

I am not able to test BOOT_COMPLETED as it is not easy to test - https://stackoverflow.com/questions/40698450/android-trying-to-test-a-service-on-boot-java-lang-securityexception-permiss

I however try to do a "fast" manual time adjustment, to fire 2 TIME_SET.

Using the following code

public class MyBroadcastReceiver extends BroadcastReceiver {
    private static final Executor dateTimeReminderExecutor = Executors.newSingleThreadExecutor();

    @Override
    public void onReceive(Context context, Intent intent) {
        Log.i("CHEOK", intent.getAction() + " : onReceive -> " + this);

        final PendingResult result = goAsync();

        dateTimeReminderExecutor.execute(() -> {
            Log.i("CHEOK", "Begin sleep -> " + this);
            try {
                Thread.sleep(20000);
            } catch (InterruptedException e) {
                e.printStackTrace();
            }
            Log.i("CHEOK", "Finish sleep -> " + this);

            try {
            } finally {
                if (result != null) {
                    result.finish();
                    Log.i("CHEOK", "result.finish() la -> " + this);
                }
            }
        });
    }
}

I obtain the following outcome, in both API 33 and API 32.

android.intent.action.TIME_SET : onReceive -> com.yocto.myapplication.MyBroadcastReceiver@9140719
Begin sleep -> com.yocto.myapplication.MyBroadcastReceiver@9140719
Finish sleep -> com.yocto.myapplication.MyBroadcastReceiver@9140719
result.finish() la -> com.yocto.myapplication.MyBroadcastReceiver@9140719
android.intent.action.TIME_SET : onReceive -> com.yocto.myapplication.MyBroadcastReceiver@92a09bf
Begin sleep -> com.yocto.myapplication.MyBroadcastReceiver@92a09bf
Finish sleep -> com.yocto.myapplication.MyBroadcastReceiver@92a09bf
result.finish() la -> com.yocto.myapplication.MyBroadcastReceiver@92a09bf

Based on the observation

1st TIME_SET will trigger BroadcastReceiver's onReceive.
2nd TIME_SET will not trigger BroadcastReceiver's onReceive, after 1st TIME_SET has called goAsync and before calling result.finish. 2nd TIME_SET will only trigger BroadcastReceiver's onReceive, after 1st TIME_SET call result.finish.
Different instances of BroadcastReceiver are used to serve 1st and 2nd TIME_SET

If that is the case, 2nd action are still "waiting" to enter RescheduleReceiver's onReceive.

2nd action might not have chance to call WorkManagerImpl's setReschedulePendingResult to "accidentally" override member variable mRescheduleReceiverResult, because the 1st action has not called mRescheduleReceiverResult.finish()

This is my very rough initial observation, and they might not hold true.

I am not able to reproduce any ANR even I have "Enable background ANR dialogs". Can you?

Thank you for your efforts.

li...@gmail.com <li...@gmail.com> #20Mar 10, 2023 01:07AM

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

Owner
Sergey Vasilinetc

Revert "Revert "Fix ANR in RescheduleReceiver""

This reverts commit 097b615030603a3c77c13e5384fca58172456f31.

Reason for revert: wrong reason to revert, spike in ANRs was wrongly attributed.

bug: 237962896
Change-Id: I622f6ae485abd87498a5c44c4a77e69b32c739e6

ya...@gmail.com <ya...@gmail.com> #21Mar 14, 2023 05:16PM

May I know when will be released for testing? Thank you.

se...@google.com <se...@google.com> #22Mar 20, 2023 12:18PM

Marked as fixed, reassigned to se...@google.com.

It will be released as 2.8.1 in upcoming days.

ya...@gmail.com <ya...@gmail.com> #23Mar 20, 2023 03:42PM

Thank you. I am looking forward the release.

ya...@gmail.com <ya...@gmail.com> #24Apr 1, 2023 04:24AM

Hi, after releasing 2.8.1 to production for more than 1 week, I can confirm that this ANR is being reduced significantly.

Thank you for being responsive in this issue.

am...@gmail.com <am...@gmail.com> #25Apr 6, 2023 09:29AM

I am using unity 2020.3.38, Admob 7.3.0 , Firebase 10.0.1
I am facing these anr Kindly help me.

Bus Sim Anr's (April 6).docx

1.1 MB

Download

az...@gmail.com <az...@gmail.com> #26Apr 18, 2023 09:32AM

The fix doesn't seem to work. I can see see ANRs happening, mostly on Samsung devices.

Edit: screenshot from Play Console "Crashes and ANRs" tab.

Message last modified on Apr 18, 2023 09:33AM

Screenshot 2023-04-18 at 13.31.47.png

81 KB

View

Download

jo...@adidas.com <jo...@adidas.com> #27May 25, 2023 04:58PM

Same for us, still happening with 2.8.1

la...@gmail.com <la...@gmail.com> #28Sep 18, 2023 01:12PM

Its still happening for us also. The fix is not fully working. It works better on samsung devices but its still doing it on Motorola and ATT devices

Issue 236906724

Description

Issue summary

Comments

se...@google.com <se...@google.com> #2Jun 23, 2022 09:37AM

jp...@samsung.corp-partner.google.com <jp...@samsung.corp-partner.google.com> #3Jun 27, 2022 01:22AM

jp...@samsung.corp-partner.google.com <jp...@samsung.corp-partner.google.com> #4Jul 4, 2022 07:57AM

se...@google.com <se...@google.com> #5Jul 6, 2022 10:30AM

jp...@gmail.com <jp...@gmail.com> #6Jul 7, 2022 02:49AM

jp...@gmail.com <jp...@gmail.com> #7Jul 15, 2022 08:59AM

jp...@gmail.com <jp...@gmail.com> #8Jul 21, 2022 08:40AM

li...@samsung.corp-partner.google.com <li...@samsung.corp-partner.google.com> #9Nov 7, 2022 08:42AM

se...@google.com <se...@google.com> #10Nov 7, 2022 12:14PM

li...@samsung.corp-partner.google.com <li...@samsung.corp-partner.google.com> #11Nov 8, 2022 03:23AM

se...@google.com <se...@google.com> #12Nov 17, 2022 10:22PM

ya...@gmail.com <ya...@gmail.com> #13Feb 21, 2023 04:44PM

ya...@gmail.com <ya...@gmail.com> #14Feb 24, 2023 03:08PM

li...@gmail.com <li...@gmail.com> #15Feb 27, 2023 01:23AM

ya...@gmail.com <ya...@gmail.com> #16Feb 27, 2023 02:59AM

ya...@gmail.com <ya...@gmail.com> #17Feb 27, 2023 03:01AM

se...@google.com <se...@google.com> #18Mar 1, 2023 02:42PM

ya...@gmail.com <ya...@gmail.com> #19Mar 1, 2023 05:21PM

li...@gmail.com <li...@gmail.com> #20Mar 10, 2023 01:07AM

ya...@gmail.com <ya...@gmail.com> #21Mar 14, 2023 05:16PM

se...@google.com <se...@google.com> #22Mar 20, 2023 12:18PM

ya...@gmail.com <ya...@gmail.com> #23Mar 20, 2023 03:42PM

ya...@gmail.com <ya...@gmail.com> #24Apr 1, 2023 04:24AM

am...@gmail.com <am...@gmail.com> #25Apr 6, 2023 09:29AM

az...@gmail.com <az...@gmail.com> #26Apr 18, 2023 09:32AM

jo...@adidas.com <jo...@adidas.com> #27May 25, 2023 04:58PM

la...@gmail.com <la...@gmail.com> #28Sep 18, 2023 01:12PM

Add comment

Issue metadata