Sudden in spike in ANR over past few days

Unity Engine
,
1

Hi, my app has just started to suffer a big rise in ANRs which seemed to start around a week or so ago. I’ve made no changes to the app myself, so it must be something external that’s caused it.

This is the error Error Information

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: 16. Wait queue head age: 11372.3ms.)

com.unity3d.player.UnityPlayerActivity

“main” prio=5 tid=1 Native | group=“” sCount=1 dsCount=0 flags=1 obj=0x744a46b8 self=0xea048000 | sysTid=5159 nice=-10 cgrp=default sched=0/0 handle=0xedc3f494 | state=S schedstat=( 1221406281 53515828 1963 ) utm=71 stm=50 core=7 HZ=100 | stack=0xff033000-0xff035000 stackSize=8MB | held mutexes= “abort lock”

#00 pc 0000000000054938 /system/lib/libc.so (nanosleep+12)

#01 pc 00000000005f5454 /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libunity.so (???)

#02 pc 0000000000696814 /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libunity.so (???)

#03 pc 000000000023e72c /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libmonobdwgc-2.0.so (mono_chain_signal+136)

#04 pc 000000000023e7e0 /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libmonobdwgc-2.0.so (???)

#05 pc 0000000000444265 /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libmonobdwgc-2.0.so (???)

#06 pc 00000000000199d4 /system/lib/libc.so (???)

#07 pc 000000000001ce32 /system/lib/libc.so (abort+54)

#08 pc 000000000034db4f /system/lib/libart.so (art::Runtime::Abort(char const*)+910)

#09 pc 00000000000071b3 /system/lib/libbase.so (android::base::LogMessage::~LogMessage()+494)

#10 pc 000000000023203f /system/lib/libart.so (art::JavaVMExt::JniAbort(char const*, char const*)+1214)

#11 pc 000000000026a109 /system/lib/libart.so (art::JNI::CallObjectMethodV(_JNIEnv*, _jobject*, _jmethodID*, std::__va_list)+1020)

#12 pc 000000000015cfa7 /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libgpg.so (ZNK3gpg13JavaReference10CallHelperIP8_jobjectEET_P7_JNIEnvMS5_FS4_S3_P10_jmethodIDSt9__va_listEPKcSD_S9+54)

#13 pc 000000000015cf27 /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libgpg.so (gpg::JavaReference::Call(gpg::JavaClass*, char const*, char const*, …) const+46)

#14 pc 00000000001600dd /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libgpg.so (gpg::AndroidGameServicesImpl::LeaderboardFetchScorePageOperation::Translate(gpg::JavaReference&&)+420)

#15 pc 00000000001608ed /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libgpg.so (???)

#16 pc 000000000016089f /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libgpg.so (???)

#17 pc 0000000000160881 /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libgpg.so (???)

#18 pc 000000000013e9f5 /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libgpg.so (???)

#19 pc 000000000015a261 /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libgpg.so (???)

#20 pc 0000000000158fcd /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libgpg.so (???)

#21 pc 0000000000158c99 /data/app/com.doofah.cubeology–h8mNF73043y7lV-ZjJ6Fg==/lib/arm/libgpg.so (gpg::NativeOnResult(_JNIEnv*, _jobject*, _jobject*)+32)

at com.google.android.gms.games.NativeSdkCallbacks.onResult (Native method)

at com.google.android.gms.common.api.internal.BasePendingResult$CallbackHandler.handleMessage (unavailable:10)

at android.os.Handler.dispatchMessage (Handler.java:106)

at android.os.Looper.loop (Looper.java:193)

at android.app.ActivityThread.main (ActivityThread.java:6718)

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:858)

It looks to me like it may be related to a Google Play Game Services Leaderboard fetch operation and it happens even with the device in airplane mode. I can’t reproduce it on any of my own devices.

Has anyone else started seeing the same behaviour or has anyone got any suggestions for a course of action to resolve this?

Many thanks

2

As I can’t get in contact with anyone that can actually reproduce this problem, I’ve no option but to just try updating to the latest version of GPGS.

It’s a bit of a pain because quite a bit has changed compared with the GPGS version I’m currently using, so I’ll have to rewrite a load of the achievements code in my app, and what’s worse is I don’t know if this will even fix the problem :frowning:

3

My crash rate has been going through the roof. It went from 5.5 crashes per 1000 devices to 800 crashes per 1000 devices. I am well into the bad behaviour threshold now. My app was hit HARD by whatever this was, and I’m not sure it will recover now.

4

Sounds like a similar rise in crashes to that which I experienced. I updated to GPGS 10.06 and it seems, judging by some feedback I’ve had, that it has fixed the problem for me.