• Hey Guest! Ever feel like entering a Game Jam, but the time limit is always too much pressure? We get it... You lead a hectic life and dedicating 3 whole days to make a game just doesn't work for you! So, why not enter the GMC SLOW JAM? Take your time! Kick back and make your game over 4 months! Interested? Then just click here!
  • Hello [name]! Thanks for joining the GMC. Before making any posts in the Tech Support forum, can we suggest you read the forum rules? These are simple guidelines that we ask you to follow so that you can get the best help possible for your issue.

Android YYC compiles but crashes on start

S

salyossy

Member
Hi,

When I build apk with VM, the game works ok, but with yyc its crashes immediately, although the build is successful...
It was no problem a few months ago, and I suspect the problem arise after 2.3 version update (maybe).
Can you help me find the problem? I'm struggling with this for days..

What it is the possible meaning of these exceptions that I get:

"
--------- beginning of crash
10-01 22:32:41.209 14881 14881 E AndroidRuntime: FATAL EXCEPTION: main
10-01 22:32:41.209 14881 14881 E AndroidRuntime: Process: com.jaxtakart.shop, PID: 14881
10-01 22:32:41.209 14881 14881 E AndroidRuntime: java.lang.RuntimeException: Unable to start receiver com.onesignal.BootUpReceiver: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.jaxtakart.shop/com.onesignal.NotificationRestoreService (has extras) }: app is in background uid UidRecord{8bb5fc8 u0a704 RCVR idle change:uncached procs:1 proclist:14881, seq(0,0,0)}
"

More detailed output::

BUILD SUCCESSFUL in 3m 7s
53 actionable tasks: 20 executed, 33 up-to-date


C:\WINDOWS\system32\cmd.exe DONE (0)
C:\WINDOWS\system32\subst.exe /d V:


C:\WINDOWS\system32\subst.exe DONE (0)
Igor complete.
device

C:\Android\sdk\platform-tools\adb -s "988a9833383749584b30" install -r "Y:/pianoMelody_5A32F707_YYC\pianoMelody.apk"
Performing Streamed Install
Success


C:\Android\sdk\platform-tools\adb DONE (0)
C:\Android\sdk\platform-tools\adb -s "988a9833383749584b30" shell am start -a android.intent.action.MAIN -n *.*.*/.RunnerActivity
Starting: Intent { act=android.intent.action.MAIN cmp=*.*.*/.RunnerActivity }


C:\Android\sdk\platform-tools\adb DONE (0)
C:\Android\sdk\platform-tools\adb -s "988a9833383749584b30" logcat yoyo:V MoPub:V DEBUG:V Ads:V MillennialMediaSDK:V AndroidRuntime:V GAV4:V *:S
--------- beginning of crash
10-01 22:32:41.209 14881 14881 E AndroidRuntime: FATAL EXCEPTION: main
10-01 22:32:41.209 14881 14881 E AndroidRuntime: Process: com.jaxtakart.shop, PID: 14881
10-01 22:32:41.209 14881 14881 E AndroidRuntime: java.lang.RuntimeException: Unable to start receiver com.onesignal.BootUpReceiver: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.jaxtakart.shop/com.onesignal.NotificationRestoreService (has extras) }: app is in background uid UidRecord{8bb5fc8 u0a704 RCVR idle change:uncached procs:1 proclist:14881, seq(0,0,0)}
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at android.app.ActivityThread.handleReceiver(ActivityThread.java:3612)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at android.app.ActivityThread.access$1300(ActivityThread.java:237)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1796)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7050)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:965)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: Caused by: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.jaxtakart.shop/com.onesignal.NotificationRestoreService (has extras) }: app is in background uid UidRecord{8bb5fc8 u0a704 RCVR idle change:uncached procs:1 proclist:14881, seq(0,0,0)}
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1666)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at android.app.ContextImpl.startService(ContextImpl.java:1611)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at android.content.ContextWrapper.startService(ContextWrapper.java:677)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at android.content.ContextWrapper.startService(ContextWrapper.java:677)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at android.support.v4.content.j.a(WakefulBroadcastReceiver.java:89)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at com.onesignal.BootUpReceiver.onReceive(BootUpReceiver.java:42)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: at android.app.ActivityThread.handleReceiver(ActivityThread.java:3603)
10-01 22:32:41.209 14881 14881 E AndroidRuntime: ... 8 more
10-04 12:04:04.401 681 681 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
10-04 12:04:04.402 681 681 F DEBUG : Build fingerprint: 'samsung/greatltexx/greatlte:9/PPR1.180610.011/N950FXXS7DSHC:user/release-keys'
10-04 12:04:04.402 681 681 F DEBUG : Revision: '9'
10-04 12:04:04.402 681 681 F DEBUG : ABI: 'arm64'
10-04 12:04:04.402 681 681 F DEBUG : pid: 30633, tid: 646, name: synthesia_main >>> com.synthesia.synthesia <<<
10-04 12:04:04.402 681 681 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
10-04 12:04:04.402 681 681 F DEBUG : Abort message: 'FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x7585ecc918)'
10-04 12:04:04.402 681 681 F DEBUG : x0 0000000000000000 x1 0000000000000286 x2 0000000000000006 x3 0000000000000008
10-04 12:04:04.402 681 681 F DEBUG : x4 0000000000008080 x5 0000000000008080 x6 0000000000008080 x7 0000000000000038
10-04 12:04:04.402 681 681 F DEBUG : x8 0000000000000083 x9 0000007610dfb828 x10 fffffff87ffffbdf x11 0000000000000001
10-04 12:04:04.402 681 681 F DEBUG : x12 0000000000000030 x13 000000005f799004 x14 000d32b0ce28c9ea x15 00002af8c04e40ea
10-04 12:04:04.402 681 681 F DEBUG : x16 0000007610e32290 x17 0000007610d718e0 x18 0000000000000000 x19 00000000000077a9
10-04 12:04:04.402 681 681 F DEBUG : x20 0000000000000286 x21 0000000000000083 x22 0000007583d36c00 x23 0000007585ecc918
10-04 12:04:04.402 681 681 F DEBUG : x24 0000000000000020 x25 0000007583d18480 x26 0000007570213420 x27 0000000000000030
10-04 12:04:04.402 681 681 F DEBUG : x28 0000000000000000 x29 00000075712f8680
10-04 12:04:04.402 681 681 F DEBUG : sp 00000075712f8640 lr 0000007610d64d28 pc 0000007610d64d54
10-04 12:04:04.410 681 681 F DEBUG :
10-04 12:04:04.410 681 681 F DEBUG : backtrace:
10-04 12:04:04.410 681 681 F DEBUG : #00 pc 0000000000021d54 /system/lib64/libc.so (abort+124)
10-04 12:04:04.411 681 681 F DEBUG : #01 pc 00000000000864d0 /system/lib64/libc.so (__fortify_fatal(char const*, ...)+120)
10-04 12:04:04.411 681 681 F DEBUG : #02 pc 0000000000085b7c /system/lib64/libc.so (HandleUsingDestroyedMutex(pthread_mutex_t*, char const*)+52)
10-04 12:04:04.411 681 681 F DEBUG : #03 pc 0000000000085a28 /system/lib64/libc.so (pthread_mutex_lock+256)
10-04 12:04:04.411 681 681 F DEBUG : #04 pc 000000000057c6ec /data/app/com.synthesia.synthesia-dao5Ok7vh8NffC-VMkAl0g==/lib/arm64/libsynthesia.so (std::__ndk1::mutex::lock()+8)
10-04 12:04:04.411 681 681 F DEBUG : #05 pc 000000000022c9ec /data/app/com.synthesia.synthesia-dao5Ok7vh8NffC-VMkAl0g==/lib/arm64/libsynthesia.so
10-04 12:04:04.411 681 681 F DEBUG : #06 pc 000000000016a42c /data/app/com.synthesia.synthesia-dao5Ok7vh8NffC-VMkAl0g==/lib/arm64/libsynthesia.so
10-04 12:04:04.411 681 681 F DEBUG : #07 pc 00000000001fa418 /data/app/com.synthesia.synthesia-dao5Ok7vh8NffC-VMkAl0g==/lib/arm64/libsynthesia.so
10-04 12:04:04.411 681 681 F DEBUG : #08 pc 00000000000eb110 /data/app/com.synthesia.synthesia-dao5Ok7vh8NffC-VMkAl0g==/lib/arm64/libsynthesia.so
10-04 12:04:04.411 681 681 F DEBUG : #09 pc 00000000000ed760 /data/app/com.synthesia.synthesia-dao5Ok7vh8NffC-VMkAl0g==/lib/arm64/libsynthesia.so
10-04 12:04:04.411 681 681 F DEBUG : #10 pc 00000000000f30cc /data/app/com.synthesia.synthesia-dao5Ok7vh8NffC-VMkAl0g==/lib/arm64/libsynthesia.so
10-04 12:04:04.411 681 681 F DEBUG : #11 pc 00000000000f7230 /data/app/com.synthesia.synthesia-dao5Ok7vh8NffC-VMkAl0g==/lib/arm64/libsynthesia.so
10-04 12:04:04.411 681 681 F DEBUG : #12 pc 0000000000232ec8 /data/app/com.synthesia.synthesia-dao5Ok7vh8NffC-VMkAl0g==/lib/arm64/libsynthesia.so
10-04 12:04:04.411 681 681 F DEBUG : #13 pc 00000000002308d0 /data/app/com.synthesia.synthesia-dao5Ok7vh8NffC-VMkAl0g==/lib/arm64/libsynthesia.so
10-04 12:04:04.411 681 681 F DEBUG : #14 pc 00000000002fbbc4 /data/app/com.synthesia.synthesia-dao5Ok7vh8NffC-VMkAl0g==/lib/arm64/libsynthesia.so
10-04 12:04:04.411 681 681 F DEBUG : #15 pc 0000000000084dc0 /system/lib64/libc.so (__pthread_start(void*)+208)
10-04 12:04:04.411 681 681 F DEBUG : #16 pc 0000000000023a4c /system/lib64/libc.so (__start_thread+68)
10-05 15:26:33.861 22963 22963 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
10-05 15:26:33.861 22963 22963 F DEBUG : Build fingerprint: 'samsung/greatltexx/greatlte:9/PPR1.180610.011/N950FXXS7DSHC:user/release-keys'
10-05 15:26:33.861 22963 22963 F DEBUG : Revision: '9'
10-05 15:26:33.861 22963 22963 F DEBUG : ABI: 'arm64'
10-05 15:26:33.861 22963 22963 F DEBUG : pid: 22632, tid: 22774, name: GLThread 21387 >>> *.*.*<<<
10-05 15:26:33.861 22963 22963 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8173b752f8
10-05 15:26:33.861 22963 22963 F DEBUG : x0 000000756ebfc500 x1 000000755acdf4c0 x2 0000000000ffffff x3 0000000000000000
10-05 15:26:33.861 22963 22963 F DEBUG : x4 0000000000000000 x5 0000000000000080 x6 6d686d71605620ff x7 000000002efb22e5
10-05 15:26:33.861 22963 22963 F DEBUG : x8 0000008173b752f0 x9 000000756e8df020 x10 0000000000001337 x11 0000000000000069
10-05 15:26:33.861 22963 22963 F DEBUG : x12 0000000000000000 x13 0000000000000000 x14 0000000000000000 x15 000000755c08dbec
10-05 15:26:33.861 22963 22963 F DEBUG : x16 0000007573b51d48 x17 0000007573677e48 x18 0000000000000007 x19 000000755ab9bd00
10-05 15:26:33.861 22963 22963 F DEBUG : x20 0000007573750660 x21 0000000000000171 x22 0000000000000001 x23 0000000000000000
10-05 15:26:33.861 22963 22963 F DEBUG : x24 0000007573c07f00 x25 0000000000000000 x26 0000007573c4b7a8 x27 000000756f2e9680
10-05 15:26:33.861 22963 22963 F DEBUG : x28 000000756f2e9678 x29 000000756f2e8dd0
10-05 15:26:33.861 22963 22963 F DEBUG : sp 000000756f2e8da0 lr 0000007573737678 pc 0000007573737680
10-05 15:26:33.947 22963 22963 F DEBUG :
10-05 15:26:33.947 22963 22963 F DEBUG : backtrace:

Any help and guideness is appretiated!! :)

[EDIT]
Additional information: I had no problem to build and run an empty project using yyc. So i guess it has something to do with code.
 
Last edited:
chirpy

chirpy

Member
It looks like something wrong in your OneSignal push notification setup (maybe it's conflicting with your android game options=build settings). If it's not an essential part of your game you can try to remove it. Otherwise, you'll need to contact your extension developer (or double check its manual), or onesignal's support.
 
S

salyossy

Member
Thank you.

The only extention used is GooglePlayAdsExtension,and I'm not using push notification at all.
Also, no premissions needed at all.. all are unmarked

What else could it be? I really have no idea.
 
Mike

Mike

nobody important
GMC Elder
There are YYC issues with 2.3 and the garbage collector.... I hit these as well. So far, it looks like they're fixed in 2.3.1.....
 
S

salyossy

Member
Mike said:
There are YYC issues with 2.3 and the garbage collector.... I hit these as well. So far, it looks like they're fixed in 2.3.1.....
Click to expand...
Those were moments of hope.. but no, I tried 2.3.1 now and it did not make any differnce, still crashes before splash.

I've been exploring this for acouple of days, comparing the log of current to previous versions, and even an empty project, and what I noticed is:
These lines repeat in EVERY attempt: even an empty project that compiles well and don't crash!
"
--------- beginning of crash
10-01 22:32:41.209 14881 14881 E AndroidRuntime: FATAL EXCEPTION: main
10-01 22:32:41.209 14881 14881 E AndroidRuntime: Process: com.jaxtakart.shop, PID: 14881
10-01 22:32:41.209 14881 14881 E AndroidRuntime: java.lang.RuntimeException: Unable to start receiver com.onesignal.BootUpReceiver: java.lang.IllegalStateException: Not allowed to start service Intent { cmp=com.jaxtakart.shop/com.onesignal.NotificationRestoreService (has extras) }: app is in background uid UidRecord{8bb5fc8 u0a704 RCVR idle change:uncached procs:1 proclist:14881, seq(0,0,0)}
"

It seems that it has nothing to do with the crash. Though it bothers me a lot, arising some questions:

*What is the meaning of "beginning of crash"?
*Why some versions with "beginning of crash" eventually crash and others do not?
*More important: if it has no impact, then WHERE in the log should I be looking for clues to my issue??

The YYC made real difference with performence comparing to VM, so its really important to me.

I think maybe I need a tip about where exactly in the log should I be looking for the real cause to the crash.

Any further help is appreciated. Please.
 
You must log in or register to reply here.
Top