Help thread for recurring crashes on build 3693 onwards

Hi all,

Intending this topic as a common thread where developers who are facing recurring crashes/ANRs that have emerged only after the API level 33 Solar2D builds can post stacktraces and other details/findings.

The idea is that this should allow @Scott_Harrison and/or @vlads to review them from a single thread and implement any fixes to the common issues. Will also be easier to help each other out.

Some crashes that I am getting across 4 apps after I pushed updates with solar2d 3693:

  1. This is being flagged by google’s pre-launch reports on a arn64-v8a device for all my apps:
  #00  pc 0x000000000004e178  /apex/ (abort+168)
  #01  pc 0x00000000000b0f70  /apex/ (__fortify_fatal(char const*, ...)+124)
  #02  pc 0x00000000000b0600  /apex/ (HandleUsingDestroyedMutex(pthread_mutex_t*, char const*)+52)
  #03  pc 0x00000000000b0498  /apex/ (pthread_mutex_lock+192)
  #04  pc 0x00000000000e9a60  /data/app/~~VuPALTyGypz6-AkK6lIl6w==/! (std::__ndk1::recursive_mutex::lock()+8)
  #05  pc 0x0000000000064168  /data/app/~~VuPALTyGypz6-AkK6lIl6w==/!
  #06  pc 0x0000000000051a18  /data/app/~~VuPALTyGypz6-AkK6lIl6w==/! (alGetError+32)
  #07  pc 0x000000000000a848  /data/app/~~VuPALTyGypz6-AkK6lIl6w==/!
  #08  pc 0x0000000000014998  /data/app/~~VuPALTyGypz6-AkK6lIl6w==/!
  #09  pc 0x00000000000af97c  /apex/ (__pthread_start(void*)+64)
  #10  pc 0x00000000000500d0  /apex/ (__start_thread+64)
  1. The second one is related to what appears to be a google signin. I am using the GPGS v3 plugin here. In testing on my own devices, it’s working fine on Android 10, 11, 13 but google has again flagged this in the pre-launch report and I also have other crash reports for this from multiple devices
Exception java.lang.SecurityException: Bad package name: com.famousdoggstudios.wg
  at ( (190800-499278674):8)
  at asoe.a ( (190800-499278674))
  at aspc.a ( (190800-499278674))
  at ( (190800-499278674):45)
  at zuj.y ( (190800-499278674):13)
  at zcu.a ( (190800-499278674):7)
  at ( (190800-499278674):4)
  at java.util.concurrent.Executors$ (
  at (
  at aalr.c ( (190800-499278674):6)
  at ( (190800-499278674):7)
  at java.util.concurrent.ThreadPoolExecutor.runWorker (
  at java.util.concurrent.ThreadPoolExecutor$ (
  at ( (190800-499278674))
  at (

Weird. Does the second one has your package name correctly in the end of the first line?

It does indeed seem weird because on the devices where I tested this after downloading from the store, I did not face any issues with any google services.

The package name is correct. Will appreciate any further insights and will also update the last post with device details if it helps

Any thoughts on the first crash stacktrace? I am seeing this more and more now for v8a ARM devices. Would appreciate if you have any tips for what I could try to resolve this.

Hi everybody!
I’ve published a version with API 33 last week and we can now measure the impact.
Feel free to ask me more info, to access my dashboard or whatever if you need.

I see crash rate increased drastically:

I see there are new kind of issues in the list:

Something related to shaders?

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 31350 >>> com.suiarts.DenturesAndDemons <<<

  #00  pc 0x0000000000079c60  /vendor/lib64/
  #01  pc 0x000000000009cf54  /vendor/lib64/
  #02  pc 0x00000000000955bc  /vendor/lib64/
  #03  pc 0x00000000000955a0  /vendor/lib64/
  #04  pc 0x00000000000955a0  /vendor/lib64/
  #05  pc 0x00000000000955a0  /vendor/lib64/
  #06  pc 0x00000000000955a0  /vendor/lib64/
  #07  pc 0x00000000000955a0  /vendor/lib64/
  #08  pc 0x0000000000097904  /vendor/lib64/
  #09  pc 0x00000000000a2968  /vendor/lib64/
  #10  pc 0x000000000010aecc  /vendor/lib64/ (GLSLCompileToUniflex+13688)
  #11  pc 0x000000000011231c  /vendor/lib64/egl/
  #12  pc 0x0000000000112eec  /vendor/lib64/egl/
  #13  pc 0x0000000000120680  /vendor/lib64/egl/ (glCompileShader+232)
  #14  pc 0x00000000000864d0  /vendor/lib64/egl/ (MEOW::meow_call_ddk_gl_2_glCompileShader(unsigned int)+32)
  #15  pc 0x000000000534f728  /data/app/~~JcLkWYogSHDeS0O0TRFXNA==/!

And here some new kind of ANRs:

@vlads can we temporarily pin this?

As you can see apps are going well above the bad behaviour threshold and I’m sure we’d all agree that one of the priorities right now will need to be to eliminate the fresh issues that have started to emerge after the api 33 support was added.

It’ll be better to have one thread than people starting new ones. Google will kill visibility/discoverability for apps that exceed the thresholds so this is quite important

Edit: if you’d prefer to alternatively create a channel on the discord server for this, I will be happy to liaise with the forum here and bring any new issues over to discord but that won’t be very efficient. Most users still use only the forum

Im getting a very high number of
Type: java.lang.IllegalArgumentException

Exception java.lang.IllegalArgumentException: parameter must be a descendant of this view
  at android.view.ViewGroup.offsetRectBetweenParentAndChild (
  at android.view.ViewGroup.offsetDescendantRectToMyCoords (
  at android.view.ViewRootImpl.scrollToRectOrFocus (
  at android.view.ViewRootImpl.draw (
  at android.view.ViewRootImpl.performDraw (
  at android.view.ViewRootImpl.performTraversals (
  at android.view.ViewRootImpl.doTraversal (
  at android.view.ViewRootImpl$ (
  at android.view.Choreographer$ (
  at android.view.Choreographer.doCallbacks (
  at android.view.Choreographer.doFrame (
  at android.view.Choreographer$ (
  at android.os.Handler.handleCallback (
  at android.os.Handler.dispatchMessage (
  at android.os.Looper.loop (
  at (
  at java.lang.reflect.Method.invoke
  at$ (
  at (

Upon googling it, its possible this is to do with admob banner? @Scott_Harrison do you have any idea?
One thing i noticed in unity is admob seem to be depreciating the smart banner and pushing the adaptive anchored banner. not sure if this correlates with the above crash.