Fatal Exception: java.util.concurrent.TimeoutException
android.media.MediaCodec.finalize() timed out after 10 seconds
I'm receiving this exception from fabric happened with Samsung Galaxy Note 3 (4.3) on the end users side, anybody has any clue on why it happened?
This crash reported by fabric. This is not related to your Application:
https://code.google.com/p/android/issues/detail?id=205978
Devices:
Samsung (62%) : GT-I9300, SM-G7105, GT-I9500, ...
LG (19%) : Nexus 4, H815, D855
Motorola (15%) : XT1058, XT1060, XT1055,...
others (4%)
Android versions:
Android 5.x : 54%
Android 4.x : 45%
Android 6.x : 1%
Following link clearly explains.
How to handle :java.util.concurrent.TimeoutException: android.os.BinderProxy.finalize() timed out after 10 seconds errors?
Related
We recently pushed two new app versions and during Googles automated testing scripts of each version we started getting new $digest errors that we have never seen before. We are not using $scope.apply() in our code anywhere. The errors are coming from just a few specific test devices running Android 8.1.0 and Android 9.
The error being reported to us:
ErrorIn = http://localhost/lib/ionic/js/ionic.bundle.js
ErrorAt = 30758 : 9
Error Array:
Message = Uncaught Error: [$rootScope:inprog] $digest already in progress
http://errors.angularjs.org/1.5.3/$rootScope/inprog?p0=%24digest
Which is the throw in the following function from that ionic.bundle.js file:
function beginPhase(phase) {
if ($rootScope.$$phase) {
throw $rootScopeMinErr('inprog', '{0} already in progress', $rootScope.$$phase); // <-- here
}
$rootScope.$$phase = phase;
}
As mentioned above, we combed through our app and verified there is no use of $scope.apply() anywhere in our code. However we do use $scope.applyAsync() in quite a few locations. Since we have never seen these before, and we have pushed MANY versions of our app, we are def baffled as to what is causing this or where in our app we may have added something that is now triggering this - BUT only on a handful of very specific Google automated test devices.
What else could be the source of $digest already in progress errors since we are able to verify that $scope.apply() is not used anywhere in our code?
Impacted devices - its only on 5 so far, but has occurred twice on three of them:
Android 8.1.0 (app_installDate : 2022-06-03, 0.40.78)
dev_UUID : ce025a1ac23adbb8
Vendor: Samsung, Device: Galaxy A70, dev_Serial : RKK021848979234
Android 8.1.0 (app_installDate : 2022-06-03, 0.40.78)
dev_UUID : ce025a1ac23adbb8
Vendor: Samsung, Device: Samsung Galaxy A70, dev_serial : RKK021848979234
Android 9 (app_installDate : 2022-06-02, 0.40.76)
dev_UUID : 26336fd5ded603b0
Vendor: Unknown, Device: GCE x86 phone, dev_serial : unknown
Android 8.1.0 (app_installDate : 2022-05-31, 0.40.76)
dev_UUID : 5558110b01a37c4c
Vendor: Vivo, Device: vivo S1, dev_serial : RKK021848979234
Android 8.1.0 (app_installDate : 2022-05-31, 0.40.76)
dev_UUID : 5558110b01a37c4c
Vendor: Vivo, Device: vivo S1, dev_serial : RKK021848979234
Android 9 (app_installDate : 2022-05-27, 0.40.76)
dev_UUID : 1e397a4762a5ea0e
Vendor: Unknown, Device: GCE x86 phone, dev_serial : unknown
Android, 8.1.0 (app_installDate : 2022-05-25, 0.40.76)
dev_UUID : a9373d8a461163a2
Vendor: Xiaomi, Device : Mi 9X, dev_serial : RKK021848979234
Android 8.1.0 (app_installDate : 2022-05-25, 0.40.76)
dev_UUID : a9373d8a461163a2
Vendor: Xiaomi, Device : Mi 9X, dev_serial : RKK021848979234
Caused by java.lang.SecurityException
Not allowed to bind to service Intent { act=com.google.android.finsky.BIND_GET_INSTALL_REFERRER_SERVICE cmp=com.android.vending/com.google.android.finsky.externalreferrer.GetInstallReferrerService }
in android project i use new library com.android.installreferrer:installreferrer:1.1
when call this code
referrerClient.startConnection(new InstallReferrerStateListener()
occure the exception
in firebase crashReporter reported this exception in
samsung (Galaxy Note3 ,Galaxy Grand2, Galaxy A7) and HUAWEI (Y5II , G750-U10)
Android 5.1
21%
Android 5.0
10%
Android 5.0.2
21%
Android 4.4.2
16%
Android 4.2.2
i check merged manifest and find this permission
android:name="com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE"
but not fount tools:remove tag
It seems to be a Google issue: There's an open ticket in their issue tracker:
https://issuetracker.google.com/issues/72926755
On Android 9, this crash appears sometimes, I can't understand why:
Fatal Exception: java.util.concurrent.TimeoutException android.media.SoundPool.finalize() timed out after 10 seconds android.media.SoundPool.native_release (SoundPool.java) android.media.SoundPool.release (SoundPool.java:177) java.lang.Thread.run (Thread.java:764)
All works perfectly before, and now on Android 9 (SONY currently), the crash appears.
Have you got some explanations guys?
I've noticed an increase in the number of StackOverflow crashes in my app which all seem to point back to Google Play Services Maps. I am currently using version 15.0.1 (com.google.android.gms:play-services-maps:15.0.1) - but this started about two weeks ago when I was still using 15.0.0. There are several crashes, but they all result in StackOverflows when dealing with Hashmaps or Arrays from the Maps code (which is obfuscated). Some examples of the crashes (I just copied the stack traces to the point where it goes to the obfuscated maps code):
Fatal Exception: java.lang.StackOverflowError: stack size 1038KB
at java.util.HashMap.remove(HashMap.java:617)
at com.google.maps.api.android.lib6.gmm6.util.e.d(:com.google.android.gms.dynamite_dynamitemodulesb#12685021#12.6.85 (040306-197041431):29)
Fatal Exception: java.lang.StackOverflowError
at java.util.ArrayList$ArrayListIterator.(ArrayList.java:551)
at java.util.ArrayList.iterator(ArrayList.java:548)
at java.util.Collections$UnmodifiableCollection$1.(Collections.java:953)
at java.util.Collections$UnmodifiableCollection.iterator(Collections.java:952)
at com.google.maps.api.android.lib6.common.i.iterator(:com.google.android.gms.dynamite_dynamitemodulesb#12685002#12.6.85 (000304-197041431):25)
Fatal Exception: java.lang.StackOverflowError: stack size 8MB
at java.util.HashMap.createEntry(HashMap.java:826)
at java.util.HashMap.addEntry(HashMap.java:813)
at java.util.HashMap.put(HashMap.java:436)
at com.google.maps.api.android.lib6.gmm6.util.e.b(:com.google.android.gms.dynamite_dynamitemodulesb#12685020#12.6.85 (040304-197041431):17)
Fatal Exception: java.lang.StackOverflowError: stack size 8MB
at java.util.HashMap.removeEntryForKey(HashMap.java:597)
at java.util.HashMap.remove(HashMap.java:584)
at com.google.maps.api.android.lib6.gmm6.util.e.d(:com.google.android.gms.dynamite_dynamitemodulesb#12685023#12.6.85 (040400-197041431):29)
Fatal Exception: java.lang.StackOverflowError: stack size 8MB
at java.util.ArrayList.(ArrayList.java:170)
at com.google.maps.api.android.lib6.common.i.(:com.google.android.gms.dynamite_dynamitemodulesb#12685020#12.6.85 (040304-197041431):9)
I also have a number of other crashes directly inside the obfuscated maps code.
Some other information: the maps are not inside the main flow of my app, so it is only used by about 8% of my users - around 200 or so calls a day. Today is by far the worst with 62 crashes affecting 13 users - two days ago it was 42 crashes and most other days I have zero crashes.
Operating system versions affected: 7.0, 6.0.1, 4.4.2, 7.1.1, 4.1.2, 5.1, 4.3
Devices: Samsung, Sony, Lenovo, Moto E3 (whatever that is) and a Huawei.
Any help or pointers would be useful!
My Android cordova-based app crashes on an Motorola Droid Turbo 2, Android Version 6.0. The app runs fine on many other devices/platforms - including my android phone. I can crash the app by making a selection in a completely barebones dropdown.
ADDITIONAL DETAILS (new 5/27/16): 1.) The app does not always crash the first time. Sometimes he can tap on 2 or 3 dropdowns. 2.) The user has another app on his phone, which I built with the same architecture, and it runs fine.
UPDATE: I finally followed USKMobility's tip and handled the whitelist error I had been getting, and got different message right before the app crashes. I have updated them in the block below.
Here are the crucial logcat lines. They start with when I tap the dropdown.
04-30 11:28:26.619: W/Adreno-GSL(9728): <gsl_ldd_control:475>: ioctl fd 38 code 0x40180917 (IOCTL_KGSL_CMDSTREAM_FREEMEMONTIMESTAMP_CTXTID) failed: errno 22 Invalid argument
04-30 11:28:26.620: W/Adreno-GSL(9728): <gsl_ldd_control:475>: ioctl fd 38 code 0x40180917 (IOCTL_KGSL_CMDSTREAM_FREEMEMONTIMESTAMP_CTXTID) failed: errno 16 Device or resource busy
04-30 11:28:26.635: I/Adreno(9728): DequeueBuffer: dequeueBuffer failed
04-30 11:28:26.692: W/google-breakpad(9728): Microdump crash handler failed.
04-30 11:28:26.707: A/libc(9728): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x7f576c0000 in tid 9780 (Chrome_InProcGp)
Another update is that I the app no longer crashes consistently on the first time I use a dropdown. Sometimes I can use 3-5 dropdowns before it crashes. Ideas?