[mono-android] debugger constantly detaches

[Sayed Arian Kooshesh]

you're running out of memory. Crank it up.

On Sat, Jun 9, 2012 at 8:07 AM, l0nestar <allan.bentham at thumbstar.com> wrote:
> Hi,
>
> I'm having serious issues debugging my application! If I start it with the
> debugger attached the app runs for about 5-10 seconds then shuts down.
> presumably because the debugger has detached.. but I cant find out why!
>
> I've looked at the logcat output.. but i dont think that it contains much
> useful information (my app was PID 2013):
>
> 06-09 13:50:13.700: D/dalvikvm(2013): GC_FOR_ALLOC freed 249K, 83% free
> 6622K/36807K, paused 11ms
> 06-09 13:50:13.700: I/dalvikvm-heap(2013): Grow heap (frag case) to 7.720MB
> for 1123216-byte allocation
> 06-09 13:50:13.720: D/dalvikvm(2013): GC_CONCURRENT freed 0K, 80% free
> 7719K/36807K, paused 1ms+1ms
> 06-09 13:50:13.800: D/dalvikvm(2013): GC_FOR_ALLOC freed 1130K, 83% free
> 6622K/36807K, paused 10ms
> 06-09 13:50:13.800: I/dalvikvm-heap(2013): Grow heap (frag case) to 7.649MB
> for 1048592-byte allocation
> 06-09 13:50:13.820: D/dalvikvm(2013): GC_CONCURRENT freed 0K, 80% free
> 7646K/36807K, paused 1ms+2ms
> 06-09 13:50:14.640: D/dalvikvm(2013): GC_CONCURRENT freed 1444K, 83% free
> 6591K/36807K, paused 1ms+3ms
> 06-09 13:50:15.510: D/dalvikvm(2013): GC_EXPLICIT freed 259K, 83% free
> 6590K/36807K, paused 2ms+3ms
> 06-09 13:50:15.510: I/monodroid-gc(2013): GC cleanup summary: 14 objects
> tested - resurrecting 0.
> 06-09 13:50:16.730: D/dalvikvm(2013): GC_CONCURRENT freed 389K, 83% free
> 6590K/36807K, paused 2ms+3ms
> 06-09 13:50:17.980: D/dalvikvm(2013): GC_CONCURRENT freed 389K, 83% free
> 6590K/36807K, paused 2ms+4ms
> 06-09 13:50:18.890: D/dalvikvm(2013): threadid=12: thread exiting, not yet
> detached (count=0)
> 06-09 13:50:19.040: D/AndroidRuntime(2084): >>>>>> AndroidRuntime START
> com.android.internal.os.RuntimeInit <<<<<<
> 06-09 13:50:19.040: D/AndroidRuntime(2084): CheckJNI is OFF
> 06-09 13:50:19.250: D/AndroidRuntime(2084): Calling main entry
> com.android.commands.am.Am
> 06-09 13:50:19.280: I/ActivityManager(191): Process com.al.triangle (pid
> 2013) has died.
> 06-09 13:50:19.280: I/WindowManager(191): WIN DEATH: Window{41361950
> com.al.triangle/hyem.Activity1 paused=false}
>
> The end of the monodroid.log contains:
>
> Finished OnTargetEvent: 1ms
> Starting OnTargetEvent: TargetExited: Backtrace: null, Thread: null,
> ProcessInfo: null
> - Finding event type..
> Entering OnTargetExited for:
> Mono.Android.VisualStudio.MonoAndroidDebuggerSession
> [D:RunShellCommand]:      015c7b47e90ffc10 am broadcast -a
> mono.android.intent.action.SEPPUKU -c
> mono.android.intent.category.SEPPUKU.com.al.triangle
> -- Start Broadcast - 09/06/2012 13:47:59 (618.0354ms) --
> [INPUT] am broadcast -a mono.android.intent.action.SEPPUKU -c
> mono.android.intent.category.SEPPUKU.com.al.triangle
> [OUTPUT]
> Broadcasting: Intent { act=mono.android.intent.action.SEPPUKU
> cat=[mono.android.intent.category.SEPPUKU.com.al.triangle] }
> Broadcast completed: result=0
> -- End Broadcast --
> - Raising event..
> Finished OnTargetEvent: 621ms
>
> and lastly visual studio dumps out:
>
> The program 'Mono' has exited with code 255 (0xff).
>
>
> My setup is win7 x64, mono for android 4.2.3, VS2010, and i'm testing on
> several devices (2.3 through to 4.04) all exhibit the same behaviour...
> (incidentally this was happening with 4.2.2 too)
>
> Without the debugger the app seems to run quite happily by itself... but I
> cant appear to attach the debugger to a running process?
>
> Im more than happy to believe my app is the underlying culprit here.. but i
> simply have no clue as to what it could be :(
>
> Has anyone encountered this or know of a work around or even how i could get
> more information to help..
>
> [mild panic and desperation :-|]
>
> Cheers,
>    Al.
>
>
>
> --
> View this message in context: http://mono-for-android.1047100.n5.nabble.com/debugger-constantly-detaches-tp5710262.html
> Sent from the Mono for Android mailing list archive at Nabble.com.
> _______________________________________________
> Monodroid mailing list
> Monodroid at lists.ximian.com
>
> UNSUBSCRIBE INFORMATION:
> http://lists.ximian.com/mailman/listinfo/monodroid



-- 
Extreme Knowledge is not something for which he programs a computer
but for which his computer is programming him.

-Wozniak