Проблема производительности #252
Updated by Victor K. almost 5 years ago
Crashlytics detected a new issue.
*Object.java* in @@
This issue is affecting at least 1 user who has crashed at least 1 time.
More information: https://fabric.io/droidoncar/android/apps/com.roher.carservice/issues/b1722342a1f7fb7ec456c96007da6674?utm_medium=service_hooks-redmine&utm_source=issue_impact
Details:
This is an Android system-level crash that happened because JVM garbage collection took too long. It was likely caused by an incorrect clean-up of native resources, or because garbage collection occurred while your app was backgrounded. Although this crash cannot be avoided, you can mitigate its effects. For more details, check out the first resource.
External resources:
"How to handle :java.util.concurrent.TimeoutException: android.os.BinderProxy.finalize() timed out after 10 seconds errors?":http://stackoverflow.com/questions/24021609/how-to-handle-java-util-concurrent-timeoutexception-android-os-binderproxy-fin
"WebView crashes on opening of popup":https://bugs.chromium.org/p/chromium/issues/detail?id=448389
"TimeoutException - timed out after 10 seconds":https://github.com/realm/realm-java/issues/1390
Stacktrace:
<pre>
Fatal Exception: java.util.concurrent.TimeoutException: android.os.Parcel.finalize() timed out after 10 seconds
at java.lang.Object.wait(Object.java)
at java.lang.Object.wait(Object.java:401)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:102)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:73)
at java.lang.Daemons$FinalizerDaemon.run(Daemons.java:170)
at java.lang.Thread.run(Thread.java:841)
</pre>