Android error

ampos · 2011-Sep-19

My app Glowing Sky Free has an "official" error report on Android Market. I hace no idea what it means orvany user feedback. Just this:

QuoteBloqueos
Actividad com.diniplay.glowingskydemo/org.libsdl.app.SDLActivity
Causa ANR keyDispatchingTimedOut
Mostrar mensajes del usuario

Marcar como antiguo
Plataformas
Droid
1 informes por semana
1 informes
Seguimientos de pilas
v2.40
19/09/2011 14:37:42
Droid
DALVIK THREADS:
"main" prio=5 tid=1 WAIT
  | group="main" sCount=1 dsCount=0 s=N obj=0x4001d8c0 self=0xccc8
  | sysTid=7062 nice=0 sched=0/0 cgrp=default handle=-1345017816
  | schedstat=( 199432379 265625001 614 )
  at java.lang.Object.wait(Native Method)
  - waiting on <0x44879d90> (a java.lang.VMThread)
  at java.lang.Object.wait(Object.java:288)
  at java.lang.Thread.join(Thread.java:983)
  at org.libsdl.app.SDLSurface.surfaceDestroyed(SDLActivity.java:448)
  at android.view.SurfaceView.reportSurfaceDestroyed(SurfaceView.java:568)
  at android.view.SurfaceView.updateWindow(SurfaceView.java:472)
  at android.view.SurfaceView.onWindowVisibilityChanged(SurfaceView.java:206)
  at android.view.View.dispatchWindowVisibilityChanged(View.java:3891)
  at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:719)
  at android.view.ViewGroup.dispatchWindowVisibilityChanged(ViewGroup.java:719)
  at android.view.ViewRoot.performTraversals(ViewRoot.java:744)
  at android.view.ViewRoot.handleMessage(ViewRoot.java:1727)
  at android.os.Handler.dispatchMessage(Handler.java:99)
  at android.os.Looper.loop(Looper.java:123)
  at android.app.ActivityThread.main(ActivityThread.java:4627)
  at java.lang.reflect.Method.invokeNative(Native Method)
  at java.lang.reflect.Method.invoke(Method.java:521)
  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:858)
  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
  at dalvik.system.NativeStart.main(Native Method)

"AudioTrackThread" prio=10 tid=10 NATIVE
  | group="main" sCount=1 dsCount=0 s=N obj=0x4487f3a8 self=0x256920
  | sysTid=7072 nice=-16 sched=0/0 cgrp=default handle=2520776
  | schedstat=( 325592023 11653961149 4051 )
  at dalvik.system.NativeStart.run(Native Method)

"Thread-10" prio=10 tid=9 NATIVE
  | group="main" sCount=1 dsCount=0 s=N obj=0x4487ab58 self=0x258230
  | sysTid=7071 nice=-8 sched=0/0 cgrp=default handle=2460816
  | schedstat=( 10111816446 18056426963 4615 )
  at android.media.AudioTrack.native_write_short(Native Method)
  at android.media.AudioTrack.write(AudioTrack.java:883)
  at org.libsdl.app.SDLActivity.audioWriteShortBuffer(SDLActivity.java:329)
  at org.libsdl.app.SDLActivity.nativeRunAudioThread(Native Method)
  at org.libsdl.app.SDLActivity$3.run(SDLActivity.java:318)
  at java.lang.Thread.run(Thread.java:1096)

"SDLThread" prio=5 tid=8 NATIVE
  | group="main" sCount=1 dsCount=0 s=Y obj=0x44879958 self=0x21e3b8
  | sysTid=7069 nice=0 sched=0/0 cgrp=default handle=2221304
  | schedstat=( 13798248382 33391540432 9951 )
  at org.libsdl.app.SDLActivity.nativeInit(Native Method)
  at org.libsdl.app.SDLMain.run(SDLActivity.java:388)
  at java.lang.Thread.run(Thread.java:1096)

"android.hardware.SensorManager$SensorThread" prio=5 tid=7 NATIVE
  | group="main" sCount=1 dsCount=0 s=Y obj=0x44876458 self=0x21ddd0
  | sysTid=7068 nice=-8 sched=0/0 cgrp=default handle=2220424
  | schedstat=( 628326404 10439971913 1847 )
  at android.hardware.SensorManager.sensors_data_poll(Native Method)
  at android.hardware.SensorManager$SensorThread$SensorThreadRunnable.run(SensorManager.java:389)
  at java.lang.Thread.run(Thread.java:1096)

"Binder Thread #2" prio=5 tid=6 NATIVE
  | group="main" sCount=1 dsCount=0 s=N obj=0x4485c1c0 self=0x125c00
  | sysTid=7067 nice=0 sched=0/0 cgrp=default handle=1172168
  | schedstat=( 15380857 100463868 37 )
  at dalvik.system.NativeStart.run(Native Method)

"Binder Thread #1" prio=5 tid=5 NATIVE
  | group="main" sCount=1 dsCount=0 s=N obj=0x4485a9f8 self=0x1196f8
  | sysTid=7066 nice=0 sched=0/0 cgrp=default handle=1152680
  | schedstat=( 12023928 260650633 33 )
  at dalvik.system.NativeStart.run(Native Method)

"Compiler" daemon prio=5 tid=4 VMWAIT
  | group="system" sCount=1 dsCount=0 s=N obj=0x448552a0 self=0x1194b8
  | sysTid=7065 nice=0 sched=0/0 cgrp=default handle=1261376
  | schedstat=( 51147460 94726562 138 )
  at dalvik.system.NativeStart.run(Native Method)

"Signal Catcher" daemon prio=5 tid=3 RUNNABLE
  | group="system" sCount=0 dsCount=0 s=N obj=0x448551e8 self=0x133d50
  | sysTid=7064 nice=0 sched=0/0 cgrp=default handle=1213512
  | schedstat=( 60943604 32348632 24 )
  at dalvik.system.NativeStart.run(Native Method)

"HeapWorker" daemon prio=5 tid=2 VMWAIT
  | group="system" sCount=1 dsCount=0 s=N obj=0x4314da80 self=0x131840
  | sysTid=7063 nice=0 sched=0/0 cgrp=default handle=1213448
  | schedstat=( 16265867 40008547 14 )
  at dalvik.system.NativeStart.run(Native Method)

MrTAToad · 2011-Sep-19

From stackover flow :

QuoteOne common cause of the "Key dispatching timed out", which I experienced quite often until digging a little deeper, is holding onto the UI thread - which handles UI events - in the debugger for more than a short amount of time (details below). For instance, if you want to debug code in your event handler, this is potential problem.

For example, if you set a breakpoint in onTouchEvent() of an Activity
class MyActivity extends Activity
{
public boolean onTouchEvent(MotionEvent me)
{
// ** Breakpoint **
// Code you wish to debug
}
}

... and you hold on to this thread (UI):

After 5 seconds you will get this warning: Key dispatching timed out sending to com.hos/com.hos.MyActivity ... null to Window ...

After 20 seconds you will get: Key dispatching timed out sending to com.hos/com.hos.MyActivity ... null to Window ... Continuing to wait for key to be dispatched

After 35 seconds you will get: Key dispatching timed out sending to com.hos/com.hos.MyActivity ... null to Window ... timed out expired process next Key & find new target

At this point, not only is the application frozen but so is the phone. Quite often I need to wait for the ANR and sometimes hard restart the phone.

So one simple answer is don't hold on to the UI thread, whether it be with the debugger or with time-expensive code.

It sounds like something is taking far too long when a key is pressed, tying up the operating system...

ampos · 2011-Sep-20

sorry?

MrTAToad · 2011-Sep-20

There is something in a key detection/pressing routine that is causing the system to stop responding.

Have you modified the java code per chance ?

ampos · 2011-Sep-20

Not as far as I remember...

Kitty Hello · 2011-Sep-20

in the latest release? Press the "trash can" icon and rebuild. Is it still there?

ampos · 2011-Sep-20

I do not worry alot. 150 download and just 1 crash.

ampos · 2011-Oct-13

Yesterday I uploaded a new version (2.71), and got 6 errors (there was only just this 1 old error).

There was errors on 2.40, 2.60 and 2.71, but I dont know (or I miss them) why they have shown now, and not before.

I will put here only the 2.71 error report, as the other, perhaps, are not relevant

QuoteFails: 1 new, 1 report
Locks: 1 new, 6 reports, 4 per week

QuoteLOCKS
ANR keyDispatchingTimedOut
en SDLActivity

QuoteFAILS
NullPointerException
en SDLActivity.onCreate()
1 error, 1 new
--------------------------

Fallo
Clase de excepción
java.lang.NullPointerException
Método de fuente
SDLActivity.onCreate()
Plataformas
OTHER

Seguimientos de pilas
v2.71
12/10/2011 05:54:43
1 informes por semana
1 informes
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.diniplay.glowingskydemo/org.libsdl.app.SDLActivity}: java.lang.NullPointerException
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2753)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2769)
at android.app.ActivityThread.access$2500(ActivityThread.java:129)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2117)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:143)
at android.app.ActivityThread.main(ActivityThread.java:4717)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:858)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
at dalvik.system.NativeStart.main(Native Method)
Caused by: java.lang.NullPointerException
at org.libsdl.app.SDLActivity.onCreate(SDLActivity.java:86)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2717)
... 11 more
Los seguimientos de pila de las aplicaciones que incluyen código ofuscado contienen nombres de símbolos ofuscados. Si se utilizó ProGuard para ofuscar la aplicación, puedes desenmascarar los seguimientos de pila utilizando la herramienta "retrace" que se incluye en la revisión 8 del kit de desarrollo de software de Android (SDK r8) y en revisiones posteriores. Para obtener más información, consulta el documento ProGuard.

MrTAToad · 2011-Oct-13

Unable to start activity ComponentInfo is to do with a problem in the the manifest.xml file or onCreate and a missing resource

News:

Android error

ampos

MrTAToad

ampos

MrTAToad

ampos

Kitty Hello

ampos

ampos

MrTAToad