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!
Related
From some devices we keep getting crash reports, with the following stack frame:
Exception java.lang.UnsatisfiedLinkError:
at java.lang.Runtime.load0 (Runtime.java:929)
at java.lang.System.load (System.java:1625)
at org.qtproject.qt5.android.QtNative$4.run (QtNative.java:505)
at org.qtproject.qt5.android.QtThread$2.run (QtThread.java:87)
at org.qtproject.qt5.android.QtThread$1.run (QtThread.java:61)
at java.lang.Thread.run (Thread.java:1012)
Unfortunately, as you may see, the stack frame nowhere mentions the missing dependency.
The crash occurs during app's initialization, not even the window gets rendered.
Qt 5.15.2
Ideas?
I am getting this error on just one particular device which is Moto E Android Version 5.1.1 which is a bit low spec then my production device Nexus 4 running same 5.1.1, most of the solutions provided here are not working, hope some one can give some pointers.
Fatal Exception: java.lang.NoSuchMethodError: No static method notEmpty(Ljava/lang/CharSequence;Ljava/lang/String;)Ljava/lang/CharSequence; in class Lorg/apache/http/util/Args; or its super classes (declaration of 'org.apache.http.util.Args' appears in /data/data/com.bowser.cloudthumper/files/instant-run/dex/slice-i2p_9eb30cacd8b3f7a68d7689d883ed4bf9afe9cdd9-classes.dex)
at org.apache.http.config.RegistryBuilder.register(RegistryBuilder.java:57)
at org.apache.http.impl.conn.BasicHttpClientConnectionManager.getDefaultRegistry(BasicHttpClientConnectionManager.java:114)
at org.apache.http.impl.conn.BasicHttpClientConnectionManager.<init>(BasicHttpClientConnectionManager.java:147)
at org.thoughtcrime.securesms.mms.LegacyMmsConnection.constructHttpClient(LegacyMmsConnection.java:181)
at org.thoughtcrime.securesms.mms.LegacyMmsConnection.execute(LegacyMmsConnection.java:194)
at org.thoughtcrime.securesms.mms.OutgoingLegacyMmsConnection.sendBytes(OutgoingLegacyMmsConnection.java:135)
at org.thoughtcrime.securesms.mms.OutgoingLegacyMmsConnection.send(OutgoingLegacyMmsConnection.java:118)
at org.thoughtcrime.securesms.mms.OutgoingLegacyMmsConnection.send(OutgoingLegacyMmsConnection.java:93)
at org.thoughtcrime.securesms.mms.CompatMmsConnection.send(CompatMmsConnection.java:37)
at org.thoughtcrime.securesms.jobs.MmsSendJob.onSend(MmsSendJob.java:82)
at org.thoughtcrime.securesms.jobs.SendJob.onRun(SendJob.java:43)
at org.thoughtcrime.securesms.jobs.MasterSecretJob.onRun(MasterSecretJob.java:18)
at org.whispersystems.jobqueue.JobConsumer.runJob(JobConsumer.java:76)
at org.whispersystems.jobqueue.JobConsumer.run(JobConsumer.java:46)
we've published our app a few days ago on Play Store. Since then, every day, we see a short burst of crashes in Crashlytics. It takes about an hour, and it generates over 200 crashes. All with same stack trace, from different devices, and all devices are rooted.
Stack trace is this (redacted):
Fatal Exception: java.lang.UnsatisfiedLinkError: Cannot load library: get_lib_extents[742]: 795 - /data/data/our.app/lib/libsomething.so is not a valid ELF object
at java.lang.Runtime.loadLibrary(Runtime.java:370)
at java.lang.System.loadLibrary(System.java:535)
Has anyone f you seen something like that? What is it?
I am working on Augmented reality app but facing Fatal error issue only on one device (Karbon Android one ) .
My code is working on other device (Samsung) without any error , but on Karbon it is giving
Fatal signal 11 (SIGSEGV) .
What can be the issue or solution for this ?
In logcat , I cant see any error even except Fatal Signal 11 .... I have searched on it and found most of time
Fatal signal error occur when you are trying to access any object which is not created at that time , but if it is the case then how my app is running on other device .
Please suggest me the solution .
Thanks..
I am trying to run the Animation3DTest , one of libgdx's test examples
On the desktop (lwjgl) I can run this test flawlessly, I can see a guy and a sword and I can move him around without any errors.
However, on Android, after starting this test, I got a force stop, and here is what showed on the Logcat
09-24 10:46:49.526 24530-24577/com.badlogic.gdx.tests.android E/AndroidRuntime﹕ FATAL EXCEPTION: GLThread 1445
com.badlogic.gdx.utils.GdxRuntimeException: File not found: com/badlogic/gdx/graphics/g3d/shaders/default.vertex.glsl (Classpath)
at com.badlogic.gdx.files.FileHandle.read(FileHandle.java:133)
at com.badlogic.gdx.backends.android.AndroidFileHandle.read(AndroidFileHandle.java:77)
at com.badlogic.gdx.files.FileHandle.length(FileHandle.java:563)
at com.badlogic.gdx.backends.android.AndroidFileHandle.length(AndroidFileHandle.java:162)
at com.badlogic.gdx.files.FileHandle.readString(FileHandle.java:192)
at com.badlogic.gdx.files.FileHandle.readString(FileHandle.java:186)
at com.badlogic.gdx.graphics.g3d.shaders.DefaultShader.getDefaultVertexShader(DefaultShader.java:249)
at com.badlogic.gdx.graphics.g3d.utils.DefaultShaderProvider.<init>(DefaultShaderProvider.java:44)
at com.badlogic.gdx.graphics.g3d.ModelBatch.<init>(ModelBatch.java:101)
at com.badlogic.gdx.tests.g3d.BaseG3dTest.create(BaseG3dTest.java:38)
at com.badlogic.gdx.tests.g3d.BaseG3dHudTest.create(BaseG3dHudTest.java:50)
at com.badlogic.gdx.tests.g3d.Animation3DTest.create(Animation3DTest.java:45)
at com.badlogic.gdx.backends.android.AndroidGraphics.onSurfaceChanged(AndroidGraphics.java:322)
at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1514)
at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1242)
Get the latest nightly build. Here's the bug report.