• 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.

specific android device crash

W

Wraithious

Guest
Hello, I've noticed very recently from my playstore reports that any Condor PGN611 Android device crashes when playing? or installing? my game, I have no info on when these crashes occur, but I do have the full error report listed below, does anyone know what this error report is stating? anyone else have problems with the Condor PGN611 device crash when playing your games? For now I can try to exclude this device on my games playstore page but I was wondering what this is all about, thanks

Code:
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

art::InvokeWithVarArgs(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, std::__va_list)

Last 7 days

Reports
3
Last 7 days
Reports total
5
Lifetime
Impacted users
3
Lifetime
Last reported
Dec 10, 1:58 PM

By app version
3005000 3
3005000 3
3005000 3 100.0%

By Android version
Android 6.0 3
Android 6.0 3 100.0%

By device
PGN611 (PGN611) 3
PGN611 (PGN611) 3 100.0%

Dec 10, 1:58 PM on app version 3005000
Condor PGN611 (PGN611), 3072MB RAM, Android 6.0
Report 1 of 3

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** pid: 0, tid: 0 >>> com.companyname.the_light_bulb_caper <<< backtrace:

#00 pc 000000000031aa2e /system/lib/libart.so (art::InvokeWithVarArgs(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, std::__va_list)+29)

#01 pc 00000000002679e9 /system/lib/libart.so (art::JNI::CallStaticObjectMethodV(_JNIEnv*, _jclass*, _jmethodID*, std::__va_list)+320)

#02 pc 00000000000f8b30 /data/app/com.companyname.the_light_bulb_caper-1/lib/arm/libyoyo.so (_JNIEnv::CallStaticObjectMethod(_jclass*, _jmethodID*, ...)+36)

#03 pc 000000000018e36c /data/app/com.companyname.the_light_bulb_caper-1/lib/arm/libyoyo.so

#04 pc 000000000018b250 /data/app/com.companyname.the_light_bulb_caper-1/lib/arm/libyoyo.so (IO_Update()+184)

#05 pc 000000000018b348 /data/app/com.companyname.the_light_bulb_caper-1/lib/arm/libyoyo.so (IO_Start_Step()+220)

#06 pc 00000000001c91fc /data/app/com.companyname.the_light_bulb_caper-1/lib/arm/libyoyo.so (DoAStep()+116)

#07 pc 00000000001ca5e8 /data/app/com.companyname.the_light_bulb_caper-1/lib/arm/libyoyo.so (MainLoop_Process()+640)

#08 pc 00000000002552a0 /data/app/com.companyname.the_light_bulb_caper-1/lib/arm/libyoyo.so (Java_com_yoyogames_runner_RunnerJNILib_Process+520)

#09 pc 000000000031d7d7 /data/app/com.companyname.the_light_bulb_caper-1/oat/arm/base.odex
 

SnoutUp

Member
I can only wish good luck with your quest, because hunting down those crashes seems like a close-to-impossible task. One advice to me was to use YYC build, which is frustratingly slow and tricky task. That said, creating YYC build might give you error about what's wrong with your code, since it's more strict. Theoretically, YYC build crash reports should also be clearer, but in my case it takes ~15 minutes just to build and it also causes crashes which were never present in a standard game build, so there's a big risk involved and that's why I haven't tried uploading it to Google Play.

Either way, I'll attempt to make a beta build with YYC some time in the future or do a production roll out to 10% of existing players to see how much better crash information is with it.
 
Last edited:
W

Wraithious

Guest
I can only wish good luck with your quest, because hunting down those crashes seems like a close-to-impossible task. One advice to me was to use YYC build, which is impossibly slow and tricky task. That said, creating YYC build might give you error about what's wrong with your code, since it's more strict. Theoretically, YYC build crash reports should also be clearer, but in my case it takes ~15 minutes just to build and it also causes crashes which were never present in a standard game build, so there's a big risk involved and that's why I haven't tried uploading it to Google Play.

Either way, I'll attempt to make a beta build with YYC some time in the future or do a production roll out to 10% of existing players to see how much better crash information is with it.
Thanks I didn't think of that, I'll try that out and see what happens
 
Top