-
Notifications
You must be signed in to change notification settings - Fork 616
ANR - art::ConditionVariable::WaitHoldingLocks #6643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
We are facing the same issue : This ANR issue has become more critical now and has severely impacted our app's performance metrics. Please find the below details: art::ConditionVariable::WaitHoldingLocks "main" tid=1 Native "FinalizerWatchdogDaemon" tid=3 Waiting "FinalizerDaemon" tid=4 Waiting "ReferenceQueueDaemon" tid=7 Waiting "GmsDynamite" tid=27 Waiting "Timer-0" tid=37 Waiting "WM.task-4" tid=59 Runnable "Okio Watchdog" tid=68 Waiting "Signal Catcher" tid=2 Runnable "perfetto_hprof_listener" tid=5 Native "Jit thread pool worker thread 0" tid=6 Native "HeapTaskDaemon" tid=8 Waiting "binder:8316_1" tid=9 Native "binder:8316_2" tid=10 Native "binder:8316_3" tid=11 Native "Profile Saver" tid=12 Native "queued-work-looper" tid=13 Native "binder:8316_5" tid=14 Native "Firebase Background Thread #0" tid=15 Waiting "pool-3-thread-1" tid=16 Waiting "DefaultDispatcher-worker-1" tid=17 Timed Waiting "binder:8316_6" tid=18 Native "Firebase Background Thread #1" tid=19 Waiting "binder:8316_7" tid=20 Native "androidx.work-3" tid=21 Waiting "DefaultDispatcher-worker-2" tid=22 Timed Waiting "DefaultDispatcher-worker-3" tid=23 Timed Waiting "Firebase Background Thread #2" tid=24 Waiting "Firebase-Messaging-Init" tid=25 Waiting "Firebase-Messaging-Topics-Io" tid=26 Waiting "androidx.work-4" tid=28 Waiting "Firebase Background Thread #3" tid=29 Waiting "MessengerIpcClient" tid=30 Waiting "WM.task-1" tid=31 Waiting "pool-15-thread-1" tid=32 Waiting "pool-15-thread-2" tid=33 Waiting "pool-15-thread-4" tid=34 Waiting "pool-15-thread-3" tid=35 Waiting "pool-17-thread-1" tid=36 Waiting "binder:8316_8" tid=38 Native "binder:8316_9" tid=39 Native "WM.task-2" tid=40 Waiting "queue-1-2" tid=41 Waiting "ConnectivityThread" tid=42 Native "pool-18-thread-1" tid=43 Waiting "binder:8316_A" tid=44 Native "pool-25-thread-1" tid=45 Waiting "pool-24-thread-5" tid=46 Waiting "pool-24-thread-3" tid=47 Waiting "pool-24-thread-4" tid=48 Waiting "pool-24-thread-2" tid=49 Waiting "queue-1-3" tid=50 Waiting "pool-24-thread-1" tid=51 Waiting "pool-24-thread-7" tid=52 Waiting "pool-24-thread-6" tid=53 Waiting "pool-24-thread-8" tid=54 Waiting "pool-26-thread-1" tid=55 Waiting "WM.task-3" tid=56 Waiting "binder:8316_B" tid=57 Native "pool-20-thread-1" tid=58 Waiting "pool-27-thread-1" tid=60 Waiting "ev" tid=61 Native "pool-19-thread-1" tid=62 Waiting "androidx.work-1" tid=63 Waiting "androidx.work-2" tid=64 Waiting "GroupHandler" tid=65 Native "Notification handler" tid=66 Native "EventBatchProcessor_Thread" tid=67 Native "binder:8316_4" tid=69 Native "binder:8316_C" tid=70 Native "binder:8316_D" tid=71 Native "binder:8316_E" tid=72 Native "binder:8316_F" tid=73 Native "binder:8316_10" tid=75 Native |
Hi folks! thank you for reporting the issue. This looks similar to #6147, as you mentioned @trungledangAxonActive. Based on this comment:
I'll raise this to our engineers. I'll get back to you once I hear from them. Thanks! |
@lehcar09 Thanks for the update! We are currently using the following Firebase services: Would the following changes help in reducing background ANRs? Awaiting your response. Thanks, |
Just to note, calling |
@trungledangAxonActive can you share your complete stack trace? |
Related to firebase#6643 ISE --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/firebase/firebase-android-sdk/issues/6643?shareId=XXXX-XXXX-XXXX-XXXX).
@lehcar09 Any updates from the engineering team? Meanwhile, is there any alternate option/solution? |
@lehcar09 Could you tell me what exactly is causing this issue? Is it because of Crashlytics, Performance, Analytics, or the Messaging service? |
Hi @lehcar09, I'm sorry for replying late because I was on my Tet Vacation in VietNam. |
@lehcar09 Did you get a chance to look into it? |
Hi folks! I consulted our engineer about this issue and per checking there is nothing in the stack trace that implicated Google Analytics for Firebase SDK. As I mentioned, I believe this is similar to issue #6147. You can refer to this comment for the investigation result on the issue. ANRs can happen for many reasons, and it is very difficult to isolate and figure out what's wrong. That said, I’ll be closing this ticket for now. If anyone can see any commonalities between these ANRs, or even better, code snippets or minimal reproducible examples, please share it with us. It'll really help us move this investigation forward. Thanks! |
Uh oh!
There was an error while loading. Please reload this page.
Issue
We're facing the ANR issue
art::ConditionVariable::WaitHoldingLocks
from our app on Android side.After researching this issue, I see that this issue was already reported on firebase-android-sdk repo: #6147.
According to this comment , it seems like this comes from
trace
function of firebase-perf module. He already created a dedicated issue on the firebase-android-sdk module: #6407 and I see that it was fixed in this PR #6431The point here is we don't use firebase-performance in our app. I also have run the
./gradlew app:dependencies
to check if we're using it but we're not.I'm not sure that the issue may come from other modules of firebase, hence please help us to take a look at this issue to see whether it does come from firebase library, and let us know if we can provide for you guys with more information.
Here's is our Stack Trace
We're using
I've also found out that there are two cases in our project that use JobScheduler:
https://developer.android.com/reference/android/app/job/JobService
Unfortunately, I've tried to reproduce it, but to no avail. This is quite difficult to reproduce.
I'll really appreciate it if you guys could give me some hints. Thanks a lot.
The text was updated successfully, but these errors were encountered: