Quick Links: Download Gideros Studio | Gideros Documentation | Gideros community chat | DONATE
Crash report on google play — Gideros Forum
  • Home
    • ›

    Crash report on google play

    XmanXman Member
    in Bugs and issues
    Almost every apps on google play have this kinds of crash:

    "main" tid=1 Blocked
    "main" prio=5 tid=1 Blocked
    | group="main" sCount=1 dsCount=0 flags=1 obj=0x75c92160 self=0xeedf9000
    | sysTid=5828 nice=-10 cgrp=default sched=0/0 handle=0xf349c4a8
    | state=S schedstat=( 754507338 26631430 1661 ) utm=48 stm=27 core=1 HZ=100
    | stack=0xff259000-0xff25b000 stackSize=8MB
    | held mutexes=
    #00 pc 0000000000019e84 /system/lib/libc.so (syscall+28)
    #01 pc 00000000000a7677 /system/lib/libart.so (art::ConditionVariable::WaitHoldingLocks(art::Thread*)+86)
    #02 pc 00000000002e0ba3 /system/lib/libart.so (_ZN3art7Monitor4LockILNS_10LockReasonE0EEEvPNS_6ThreadE+3122)
    #03 pc 00000000002e2533 /system/lib/libart.so (art::Monitor::Wait(art::Thread*, long long, int, bool, art::ThreadState)+1058)
    #04 pc 00000000002e38d1 /system/lib/libart.so (art::Monitor::Wait(art::Thread*, art::mirror::Object*, long long, int, bool, art::ThreadState)+320)
    #05 pc 00000000002f84c1 /system/lib/libart.so (art::Object_waitJI(_JNIEnv*, _jobject*, long long, int)+36)
    at java.lang.Object.wait (Native method)
    - waiting to lock <0x0f84b094> (a java.util.ArrayList) held by thread 11
    at java.lang.Object.wait (Object.java:422)
    at com.giderosmobile.android.player.GiderosApplication.onPause (GiderosApplication.java:547)
    - locked <0x0f84b094> (a java.util.ArrayList)
    at com.giderosmobile.android.checkersActivity.onPause (checkersActivity.java:177)
    at android.app.Activity.performPause (Activity.java:7646)
    at android.app.Instrumentation.callActivityOnPause (Instrumentation.java:1469)
    at android.app.ActivityThread.performPauseActivityIfNeeded (ActivityThread.java:4258)
    at android.app.ActivityThread.performPauseActivity (ActivityThread.java:4223)
    at android.app.ActivityThread.handlePauseActivity (ActivityThread.java:4175)
    at android.app.servertransaction.PauseActivityItem.execute (PauseActivityItem.java:45)
    at android.app.servertransaction.TransactionExecutor.executeLifecycleState (TransactionExecutor.java:145)
    at android.app.servertransaction.TransactionExecutor.execute (TransactionExecutor.java:70)
    at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1955)
    at android.os.Handler.dispatchMessage (Handler.java:106)
    at android.os.Looper.loop (Looper.java:214)
    at android.app.ActivityThread.main (ActivityThread.java:7076)
    at java.lang.reflect.Method.invoke (Native method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)
    at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:965)
    +1 -1Share on Facebook

    Comments

    • olegoleg Member
      edited November 2019
      Open a 'test report' and click on 'luac'




      https://support.google.com/googleplay/android-developer/answer/3131213?hl=en
      image.png
      805 x 722 - 82K
      my games:
      https://play.google.com/store/apps/developer?id=razorback456
      мій блог по гідерос https://simartinfo.blogspot.com
      Слава Україні!
      +1 -1Share on Facebook
    • SinisterSoftSinisterSoft Maintainer
      edited November 2019
      @Xman If you get @hgy29 's firebase plugin (a 'must buy' if you are serious) then you will see the lua syntax error in crashlytics (or whatever it's called :) )...
      Coder, video game industry veteran (since the '80s, ❤'s assembler), arrested - never convicted hacker (in the '90s), dad of five, he/him (if that even matters!).
      https://deluxepixel.com
      +1 -1Share on Facebook
    • olegoleg Member
      edited November 2019
      SinisterSoft said:

      @Xman If you get @hgy29 's firebase plugin (a 'must buy' if you are serious) then you will see the lua syntax error in crashlytics (or whatever it's called :) )...

      I do not use 'firebase plugin', lua syntax report is in google test report.
      image

      ps//Guys, if you publish the documentation for the 'firebase' plugin in the wiki - then you will have more sales.
      qqqq.PNG
      983 x 577 - 66K
      my games:
      https://play.google.com/store/apps/developer?id=razorback456
      мій блог по гідерос https://simartinfo.blogspot.com
      Слава Україні!
      +1 -1Share on Facebook
    • XmanXman Member
      edited November 2019
      Are your games made by Gideros have this kinds of crash in google play?
      I do not think it's caused by my scripts. Because it crashed in only a small part of the users.
      +1 -1Share on Facebook
    • hgy29hgy29 Maintainer
      edited November 2019 Accepted Answer
      I see
      at java.lang.Object.wait (Object.java:422)
at com.giderosmobile.android.player.GiderosApplication.onPause (GiderosApplication.java:547)
- locked <0x0f84b094> (a java.util.ArrayList)
      It means that the app was being put into background or othewise deactivated by the system, and that for some reason it couldn't acquire a lock in due time, thus Android killed it. Most probably the user didn't see anything.

      Anyhow it would interesting to see the stack trace of that other thread, to understand why it didn't release that lock fast enough.
      +1 -1Share on Facebook
    • XmanXman Member
      Oh, I see.
      I did not see any user reviews about the crash.
      However, too many crash will have bad effect on the ranking for the game.
      Will it be possible to avoid this kinds of crash?
      +1 -1Share on Facebook
    • XmanXman Member
      edited November 2019
      "GLThread 994" prio=5 tid=11 Native
      | group="main" sCount=1 dsCount=0 flags=1 obj=0x16e810f0 self=0xe749c200
      | sysTid=5852 nice=0 cgrp=default sched=0/0 handle=0xd1cff970
      | state=R schedstat=( 47370637466 736109183 25576 ) utm=3455 stm=1281 core=5 HZ=100
      | stack=0xd1bfc000-0xd1bfe000 stackSize=1042KB
      | held mutexes=
      #00 pc 0000000000056a20 /system/lib/libc.so (sched_yield+12)
      #01 pc 00000000001d4d8d /data/app/com.XXXXXXX.XXXXXXXX-qmlNgZfcmueS9xkSJPmfDw==/lib/arm/libgideros.so (???)
      #02 pc 00000000001c96c1 /data/app/com.XXXXXXX.XXXXXXXX-qmlNgZfcmueS9xkSJPmfDw==/lib/arm/libgideros.so (alcDevicePauseSOFT+112)
      #03 pc 0000000000097caf /data/app/com.XXXXXXX.XXXXXXXX-qmlNgZfcmueS9xkSJPmfDw==/lib/arm/libgideros.so (ApplicationManager::pause()+102)
      at com.giderosmobile.android.player.GiderosApplication.nativePause (Native method)
      at com.giderosmobile.android.player.GiderosApplication.onDrawFrame (GiderosApplication.java:668)
      - locked <0x0d464200> (a java.lang.Object)
      at com.giderosmobile.android.GiderosRenderer.onDrawFrame (checkersActivity.java:424)
      at android.opengl.GLSurfaceView$GLThread.guardedRun (GLSurfaceView.java:1571)
      at android.opengl.GLSurfaceView$GLThread.run (GLSurfaceView.java:1270)
      +1 -1Share on Facebook
    • XmanXman Member
      Too many other thread stacks to post here.
      +1 -1Share on Facebook
    • olegoleg Member
      Xman said:

      Are your games made by Gideros have this kinds of crash in google play?

      No
      my games:
      https://play.google.com/store/apps/developer?id=razorback456
      мій блог по гідерос https://simartinfo.blogspot.com
      Слава Україні!
      +1 -1Share on Facebook
    • XmanXman Member
      I have get the following two reports have the same above stack trace:


      1.
      Broadcast of Intent { act=android.intent.action.SCREEN_OFF flg=0x50200010 (has extras) }

      2.
      Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago. Wait queue length: 2. Wait queue head age: 6619.9ms.), happend at time = 778313128@#@18697
      +1 -1Share on Facebook
    • hgy29hgy29 Maintainer
      Xman said:


      #02 pc 00000000001c96c1 /data/app/com.XXXXXXX.XXXXXXXX-qmlNgZfcmueS9xkSJPmfDw==/lib/arm/libgideros.so (alcDevicePauseSOFT+112)

      This one is a different kind: https://github.com/gideros/gideros/issues/450
      I tried to track it down multiple times, but couldn't find an explanation.

      For the first one you posted, can you add it to github issues with full stack trace of all threads ?

      +1 -1Share on Facebook
    • XmanXman Member
      posted:
      https://github.com/gideros/gideros/issues/480
      +1 -1Share on Facebook
    Sign In or Register to comment.