Thanks Jon, I tried some of those options, they dont appear to show the app doing anything particularly odd. Is there a specific one you were thinking i should try?
I intermittently get this error when the debugger detaches. http://mono-for-android.1047100.n5.nabble.com/file/n5710267/monodebugexception.png monodebugexception.png I was also wondering if it is possible that the android OS is shutting my app down for misbehaving? If this is the case logcat doesnt appear to have any clues (im assuming the log after 'Process com.al.triangle (pid 9949) has died.' is just android cleaning up the aftermath..) ------ 06-10 14:45:43.520: D/dalvikvm(9949): GC_CONCURRENT freed 388K, 83% free 6590K/36743K, paused 2ms+3ms 06-10 14:45:44.630: D/dalvikvm(9949): GC_CONCURRENT freed 388K, 83% free 6590K/36743K, paused 1ms+1ms 06-10 14:45:45.740: D/dalvikvm(9949): GC_CONCURRENT freed 388K, 83% free 6590K/36743K, paused 1ms+2ms 06-10 14:45:45.970: D/dalvikvm(9949): threadid=12: thread exiting, not yet detached (count=0) 06-10 14:45:46.080: D/AndroidRuntime(10017): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<< 06-10 14:45:46.080: D/AndroidRuntime(10017): CheckJNI is OFF 06-10 14:45:46.310: D/AndroidRuntime(10017): Calling main entry com.android.commands.am.Am 06-10 14:45:46.340: I/ActivityManager(191): Process com.al.triangle (pid 9949) has died. 06-10 14:45:46.340: I/WindowManager(191): WIN DEATH: Window{41396498 com.al.triangle/hyem.Activity1 paused=false} 06-10 14:45:46.340: W/WindowManager(191): Force-removing child win Window{413e1c08 SurfaceView paused=false} from container Window{41396498 com.al.triangle/hyem.Activity1 paused=false} 06-10 14:45:46.340: W/ActivityManager(191): Force removing ActivityRecord{4131b068 com.al.triangle/hyem.Activity1}: app died, no saved state 06-10 14:45:46.340: W/WindowManager(191): Failed looking up window 06-10 14:45:46.340: W/WindowManager(191): java.lang.IllegalArgumentException: Requested window android.os.BinderProxy@4131bd48 does not exist 06-10 14:45:46.340: W/WindowManager(191): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:7156) 06-10 14:45:46.340: W/WindowManager(191): at com.android.server.wm.WindowManagerService.windowForClientLocked(WindowManagerService.java:7147) 06-10 14:45:46.340: W/WindowManager(191): at com.android.server.wm.WindowState$DeathRecipient.binderDied(WindowState.java:1529) 06-10 14:45:46.340: W/WindowManager(191): at android.os.BinderProxy.sendDeathNotice(Binder.java:417) 06-10 14:45:46.340: W/WindowManager(191): at dalvik.system.NativeStart.run(Native Method) 06-10 14:45:46.340: I/WindowManager(191): WIN DEATH: null 06-10 14:45:46.350: D/AndroidRuntime(10017): Shutting down VM 06-10 14:45:46.360: D/dalvikvm(10017): GC_CONCURRENT freed 103K, 81% free 489K/2560K, paused 0ms+1ms 06-10 14:45:46.360: D/dalvikvm(10017): Debugger has detached; object registry had 1 entries 06-10 14:45:46.410: W/InputManagerService(191): Got RemoteException sending setActive(false) notification to pid 9949 uid 10043 06-10 14:45:46.480: D/Zygote(107): Process 9949 exited cleanly (255) -- View this message in context: http://mono-for-android.1047100.n5.nabble.com/debugger-constantly-detaches-tp5710262p5710267.html Sent from the Mono for Android mailing list archive at Nabble.com. _______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
