Android Question Strange crash

GiovanniPolese

Well-Known Member
Licensed User
Longtime User
Hi
I have a weird behaviour on an app. It crashes in release mode, but not in debug mode. Therefore I don't know what to do. If somebody have any knowledge, I attach the log obtained in release mode, totally useless for me to resolve the problem. Thanks for any hint.
 

Attachments

  • error.txt
    19.8 KB · Views: 37
Solution
I want to be clear that I am not an expert in understanding these logs. But for entertainment, and possible help, I am willing to share how far I got. :)

This is a short section of the log:
backtrace:
#00 pc 000000000004eee4  /apex/com.android.runtime/lib64/bionic/libc.so (__memcpy+292) (BuildId: 3bb3bed8953efcf72e0c16e90a83355e)
#01 pc 000000000081cff4  /vendor/lib64/egl/libGLES_mali.so (BuildId: 730efa64d22beddc2099f2051002ae63)
#02 pc 000000000083997c  /vendor/lib64/egl/libGLES_mali.so (BuildId: 730efa64d22beddc2099f2051002ae63)
#03 pc 000000000082a500  /vendor/lib64/egl/libGLES_mali.so (BuildId: 730efa64d22beddc2099f2051002ae63)
#04 pc 00000000007bac34  /vendor/lib64/egl/libGLES_mali.so (BuildId: 730efa64d22beddc2099f2051002ae63)
#05...

Sandman

Expert
Licensed User
Longtime User
I want to be clear that I am not an expert in understanding these logs. But for entertainment, and possible help, I am willing to share how far I got. :)

This is a short section of the log:
backtrace:
#00 pc 000000000004eee4  /apex/com.android.runtime/lib64/bionic/libc.so (__memcpy+292) (BuildId: 3bb3bed8953efcf72e0c16e90a83355e)
#01 pc 000000000081cff4  /vendor/lib64/egl/libGLES_mali.so (BuildId: 730efa64d22beddc2099f2051002ae63)
#02 pc 000000000083997c  /vendor/lib64/egl/libGLES_mali.so (BuildId: 730efa64d22beddc2099f2051002ae63)
#03 pc 000000000082a500  /vendor/lib64/egl/libGLES_mali.so (BuildId: 730efa64d22beddc2099f2051002ae63)
#04 pc 00000000007bac34  /vendor/lib64/egl/libGLES_mali.so (BuildId: 730efa64d22beddc2099f2051002ae63)
#05 pc 0000000000375da8  /data/misc/apexdata/com.android.art/dalvik-cache/arm64/boot.oat (art_jni_trampoline+120)
#06 pc 0000000000090190  /data/app/~~NQ7no70bCXA-Rr_dfKAEpw==/Geoide.GOrto-OAm5FMy8nMYIO1AbxkocBQ==/oat/arm64/base.odex (anywheresoftware.b4a.agraham.opengl2.GLWrapper2.glDrawArrays+48)
  • Your log contains three separate crashes (excerpt above from first one)
  • It seems you're using the OpenGL 2.0 library from @agraham
  • The crashes seems to happen in GLWrapper2.glDrawArrays
    • ...which means that it's possible (but not certain) that this is a problem that is because of an issue in the OpenGL library
  • The OpenGL library leads to libGLES_mali.so. If one search for that, together with SEGV_ACCERR (mentioned in the log), one of the hits is this page, which at least suggests that the user has not given all permissions - so perhaps double check that all is approved?
  • All crashes seem to happen in your sub drawdashed2d, so perhaps add extra logging and error checking in there to get more info?
Well, that's how far I got. I'd love if somebody really good at this could tell me if I got anything wrong - and what I missed. :)
 
Upvote 0
Solution

GiovanniPolese

Well-Known Member
Licensed User
Longtime User
Hi Sandman. Your hints may be useful. At least I can do some trials on the sub that you identified. I will inform you as soon as I will do these tests. Thanks a lot.
 
Upvote 0

GiovanniPolese

Well-Known Member
Licensed User
Longtime User
Hello Sandman. Despite all, your indication was useful, so I marked your answer as solution. In these condizions, it is very unlikely that somebody may give more useful indications. Much probably, as usual, the problem is in my code calling OpenGl, not in OpenGL itself. Thanks.
 
Upvote 0
Top