-
Notifications
You must be signed in to change notification settings - Fork 614
art::ConditionVariable::WaitHoldingLocks(art::Thread*) #4985
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. |
Hey @trong-le123, thanks for reaching out. Not sure what the issue is here, I've tried testing the latest version of Crashlytics and it seems to work fine. Could you provide a minimal reproducible example of your issue? It'll help speed up our investigation. Thanks! |
Unfortunately I don't have any code stripped down enough to share. Is there anything else I can provide to help with clarity? |
Something seems to be conflicting with Crashlytics when it is trying to write logs Could you help answer a few questions below:
|
|
Thanks for the extra details, @trong-le123. In expectation, Crashlytics shouldn't be causing ANRs by writing logs, so I'm guessing something is triggering this, perhaps the multiple API server calls are causing too much of I/O operations on the main thread which in turn is causing IO Root blocking. You could try using StrictMode to detect any operations causing issues. However, without any code snippets or MCVE, it is difficult to determine the exact cause of your issue. |
main (native):tid=1 systid=20388 im using firebase crashlytics |
Hi @krunalpatel3, your issue seems to be different from the current issue. Could you file a new issue with details according to our template? It'll help us conduct an initial investigation regarding your issue. Thanks! |
Hey @trong-le123. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically. If you have more information that will help us get to the bottom of this, just add a comment! |
Since there haven't been any recent updates here, I am going to close this issue. @trong-le123 if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this. |
Libraries used:
implementation 'com.google.firebase:firebase-crashlytics:18.3.7'
implementation 'com.google.firebase:firebase-core:21.1.1'
implementation 'com.google.firebase:firebase-analytics:21.2.2'
implementation 'com.google.firebase:firebase-messaging:23.1.2'
Issue
I am running into a issue where the app spins for a while and then ends up crashing with an ANR dialog.
Crashlytics Exception Handler1 (runnable):tid=19 systid=10160
at libcore.io.ForwardingOs.fdatasync(ForwardingOs.java:256)
at android.system.Os.fdatasync(Os.java:187)
at java.io.RandomAccessFile.maybeSync(RandomAccessFile.java:306)
at java.io.RandomAccessFile.writeBytes(RandomAccessFile.java:547)
at java.io.RandomAccessFile.write(RandomAccessFile.java:559)
at com.google.firebase.crashlytics.internal.metadata.QueueFile.writeHeader(QueueFile.java:58)
at com.google.firebase.crashlytics.internal.metadata.QueueFile.add(QueueFile.java:91)
at com.google.firebase.crashlytics.internal.metadata.QueueFile.add(QueueFile.java:91)
at com.google.firebase.crashlytics.internal.metadata.QueueFileLogStore.doWriteToLog(QueueFileLogStore.java:90)
at com.google.firebase.crashlytics.internal.metadata.QueueFileLogStore.writeToLog(QueueFileLogStore.java:90)
at com.google.firebase.crashlytics.internal.metadata.LogFileManager.writeToLog(LogFileManager.java:28)
at com.google.firebase.crashlytics.internal.common.CrashlyticsController$5.call(CrashlyticsController.java:28)
at com.google.firebase.crashlytics.internal.common.CrashlyticsController$5.call(CrashlyticsController.java:28)
at com.google.firebase.crashlytics.internal.common.CrashlyticsBackgroundWorker$3.then(CrashlyticsBackgroundWorker.java:2)
at com.google.android.gms.tasks.zzc.run(zzc.java:70)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
at com.google.firebase.crashlytics.internal.common.ExecutorUtils$1$1.onRun(ExecutorUtils.java:2)
at com.google.firebase.crashlytics.internal.common.BackgroundPriorityRunnable.run(BackgroundPriorityRunnable.java:5)
at java.lang.Thread.run(Thread.java:1012)
That is the error returned and the rest of the log is different threads be ran
The text was updated successfully, but these errors were encountered: