Crashing on Android

Development Platform & Builds Mobile
, , , ,
1

Hello, we’ve been experiencing crashes on certain android devices, here’s a call stack, anyone having the same experience ?

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: '/shamu/shamu:6.0.1/MOB30I/2756745:/release-keys'
Revision: '0'
ABI: 'arm'
pid: 31169, tid: 31186, name: Thread-2305 
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: 'Invalid address 0x8c7f3880 passed to free: value not allocated'
r0 00000000 r1 000079d2 r2 00000006 r3 95eda978
r4 95eda980 r5 95eda930 r6 00000000 r7 0000010c
r8 b09bd648 r9 b6d6b594 sl 00000001 fp 95ed5fa8
ip 00000006 sp 95ed5e40 lr b6d35b61 pc b6d37f50 cpsr 40070010

backtrace:
#00 pc 00041f50 /system/lib/libc.so (tgkill+12)
#01 pc 0003fb5d /system/lib/libc.so (pthread_kill+32)
#02 pc 0001c30f /system/lib/libc.so (raise+10)
#03 pc 000194c1 /system/lib/libc.so (__libc_android_abort+34)
#04 pc 000174ac /system/lib/libc.so (abort+4)
#05 pc 0001af23 /system/lib/libc.so (__libc_fatal+16)
#06 pc 00055373 /system/lib/libc.so (ifree+202)
#07 pc 00058257 /system/lib/libc.so (je_free+374)
#08 pc 0000e71f /system/lib/libutils.so (_ZNK7android7RefBase9decStrongEPKv+50)
#09 pc 00009811 /system/lib/libwilhelm.so
#10 pc 00013f89 /system/lib/libwilhelm.so
#11 pc 00018fe3 /system/lib/libwilhelm.so
#12 pc 03603738 /data/app/com.ScoreStudios.RaidTactics-2/lib/arm/libUE4.so (_ZN16FSLESSoundSource4StopEv+108)
#13 pc 01a1a938 /data/app/com.ScoreStudios.RaidTactics-2/lib/arm/libUE4.so (_ZN12FAudioDevice11StopSourcesER6TArrayIP13FWaveInstance17FDefaultAllocatorEi+428)
#14 pc 01a1af74 /data/app/com.ScoreStudios.RaidTactics-2/lib/arm/libUE4.so (_ZN12FAudioDevice6UpdateEb+764)
#15 pc 01a28b90 /data/app/com.ScoreStudios.RaidTactics-2/lib/arm/libUE4.so (_ZN19FAudioDeviceManager24UpdateActiveAudioDevicesEb+56)
#16 pc 01bb21cc /data/app/com.ScoreStudios.RaidTactics-2/lib/arm/libUE4.so (_ZN11UGameEngine4TickEfb+1956)
#17 pc 015202e0 /data/app/com.ScoreStudios.RaidTactics-2/lib/arm/libUE4.so (_ZN11FEngineLoop4TickEv+2672)
#18 pc 0151daa0 /data/app/com.ScoreStudios.RaidTactics-2/lib/arm/libUE4.so (_Z11AndroidMainP11android_app+2784)
#19 pc 015211b0 /data/app/com.ScoreStudios.RaidTactics-2/lib/arm/libUE4.so (android_main+116)
#20 pc 015350f8 /data/app/com.ScoreStudios.RaidTactics-2/lib/arm/libUE4.so
#21 pc 0003f45f /system/lib/libc.so (_ZL15__pthread_startPv+30)
#22 pc 00019b43 /system/lib/libc.so (__start_thread+6)

Here are the devices that are experiencing the crash

LG Sunset
Samsung Galaxy Prime
Nexus 6
LG G3
Galaxy Tab3 Lite
2

It is a C++ project, yeah, can’t really tell if we’re using sound wrongly or if there’s a bug with sound on android.

3

Is this C++ project?
From stack it seems to be sound related issue

4

crash happens in libwilhelm.so which seems to be sound library. Do you touch any sound related stuff in C++? I don’t see any sign of your code to be involved, but crash could be caused by indirecly

5

Hey Polytopey,

Could you provide us with step by step reproduction steps on setting up the sound within your project? Or perhaps submit a sample project with the same sound set up within it?

Signal 6 is the issue that I see within the logs you did provide. This typically is an abort from the program due to memory allocation. I’d like to see if this is the same error in each of your devices.

Could you attach the logs from each of your mobile devices with your next reply?

  • Attach your phone to the computer
  • Go here: C:\android-sdk-windows\tools
  • Open up Monitor.bat
  • Launch the program and save the logs

If you cannot get Monitor.bat to open, please go to:

  • C:\android-sdk-windows\tools\lib\monitor-x86
  • Open up Monitor.exe
  • Follow the instructions above

Make sure that you highlight all of the logs, because they do not save unless they’re highlighted.

Thank you!

6

Hey Polytopey,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you!