Some customers are reporting ANRs, which we can not reproduce.

Most of the times when various activity/fragment is resuming/creating.

Usually something like this:

02 pc 00012e10 /system/lib/ (__pthread_cond_timedwait+60)

#03 pc 0012bbc8 /data/data/com.workinfield/lib/ (_wapi_handle_timedwait_signal_handle+420)
at Method)
at bzing.client.droid.usercontrols.VehicleSelectorControl.(
at java.lang.reflect.Constructor.constructNative(Native Method)
at java.lang.reflect.Constructor.newInstance(
at android.view.LayoutInflater.createView(
at android.view.LayoutInflater.createViewFromTag(


Or like this:

"main" prio=5 tid=1 NATIVE
| group="main" sCount=1 dsCount=0 obj=0x41af1508 self=0x41ae1660
| sysTid=9210 nice=0 sched=0/0 cgrp=[no-cpu-subsys] handle=1075015472
| schedstat=( 4703796375 2665374723 5094 ) utm=374 stm=96 core=1
#00 pc 0000dc84 /system/lib/ (__futex_syscall3+12)
#01 pc 00012db4 /system/lib/ (__pthread_cond_timedwait_relative+48)
#02 pc 00012e10 /system/lib/ (__pthread_cond_timedwait+60)
#03 pc 0012bbc8 /data/data/com.workinfield/lib/ (_wapi_handle_timedwait_signal_handle+420)
at bzing.client.droid.fragments.NewTripFragment.n_onActivityCreated(Native Method)
at bzing.client.droid.fragments.NewTripFragment.onActivityCreated(
at ...

They have rapidly increased after update to 4.10 branch, but not sure if problem is in Xamarin or in our code.

How resolve them ? Some customers are getting these 100% of the time, uninstalling our app.

What is "/data/data/com.workinfield/lib/ (_wapi_handle_timedwait_signal_handle+420)" ?


Sign In or Register to comment.