Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

jdk.internal.misc.Unsafe.park (Native method) crash in android app

I am facing this issue in android app jdk.internal.misc.Unsafe.park (Native method)

There are several answers in stackoverflow but i need in android specific way

main (waiting): tid=1 systid=14525 
   at jdk.internal.misc.Unsafe.park(Native method)
   at java.util.concurrent.locks.LockSupport.park(LockSupport.java:194)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:885)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:917)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1240)
   at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:267)
   at com.google.android.gms.common.api.internal.zabe.zai(com.google.android.gms:play-services-base@@18.0.1:1)
   at com.google.android.gms.common.api.internal.zabd.zaa(com.google.android.gms:play-services-base@@18.0.1:2)
   at com.google.android.gms.common.api.internal.zabx.onReceive(com.google.android.gms:play-services-base@@18.0.1:4)
   at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0$LoadedApk$ReceiverDispatcher$Args(LoadedApk.java:1752)
   at android.app.LoadedApk$ReceiverDispatcher$Args$$ExternalSyntheticLambda0.run(unavailable:2)
   at android.os.Handler.handleCallback(Handler.java:938)
   at android.os.Handler.dispatchMessage(Handler.java:99)
   at android.os.Looper.loopOnce(Looper.java:233)
   at android.os.Looper.loop(Looper.java:344)
   at android.app.ActivityThread.main(ActivityThread.java:8191)
   at java.lang.reflect.Method.invoke(Native method)
   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:584)
   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1034)
like image 285
RockyGlobal Avatar asked Sep 06 '25 07:09

RockyGlobal


1 Answers

I got this issue too. In my case it was an ANR caused by not properly requesting location. I was using an outdated library to do that. Once I moved out of the library and used the Android recommended way of querying the current location it worked fine.

Problematic Library: https://github.com/mcharmas/Android-ReactiveLocation

Android recommended way of querying current location: https://developer.android.com/training/location/retrieve-current

like image 174
Eduardo Maia Avatar answered Sep 07 '25 19:09

Eduardo Maia