Bug 6450 - MD freezes while debugging on Simulator
Summary: MD freezes while debugging on Simulator
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 3.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2012-08-07 12:18 UTC by guivho
Modified: 2013-01-25 13:06 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
MonoDevelop logfile after kill -QUIT (6.49 MB, application/text)
2012-08-07 12:18 UTC, guivho
Details
Activity monitor problem report info (57.49 KB, application/zip)
2012-09-13 07:44 UTC, guivho
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description guivho 2012-08-07 12:18:50 UTC
Created attachment 2316 [details]
MonoDevelop logfile after kill -QUIT

When debugging on the simulator, my MD usually freezes after a varying
period of inactivity. I want it to just keep running to catch any
crashes, but it just freezes.

The recipe is simple. I just start debugging the app, don't do
anything on the keyboard or wit the mouse, and after a while (seconds,
minutes...) MD and the Simulator are just frozen: the little rainbow
wheel keeps spinning ...

I have to kill the MD process (kill -KILL pid) to recover.

This may wel be caused by the app, still it is very annoying. It has as
side effect that I seldom run in debug mode, and usually do my debugging
bmo console otput at strategic places.

Version informationn follows (allthough this is not a recent problem: it
has plagued me for as long as I can remember)

MonoDevelop 3.0.3.5
Installation UUID: 7981a2f1-e51d-4ee9-941a-f90b2222409b
Runtime:
        Mono 2.10.9 (tarball)
        GTK 2.24.10
        GTK# (2.12.0.0)
        Package version: 210090011
Apple Developer Tools:
         Xcode 4.3.3 (1178)
         Build 4E3002
Monotouch: 5.2.12
Mono for Android: 4.2.4.167234518 (Evaluation)
Android SDK not found.
Build information:
        Release ID: 30003005
        Git revision: 3d53e1366933298a3fe0cdc6d0f7d00c9916564c-dirty
        Build date: 2012-07-27 19:06:34+0000
        Xamarin addins: 73ecde7c48d943adb6e33d511d3cf0661d006801
Operating System:
        Mac OS X 10.7.4
        Darwin zac.local 11.4.0 Darwin Kernel Version 11.4.0
            Mon Apr  9 19:32:15 PDT 2012
            root:xnu-1699.26.8~1/RELEASE_X86_64 x86_64

Ther's been an email thread about this at url
http://lists.ximian.com/pipermail/monodevelop-list/2012-August/014985.html

On 6 August 2012 19:20, Rolf Bjarne Kvinge <rolf at xamarin.com> wrote:
> Hi,
>
> This is more for the monodevelop list, but in any case: when this happens,
> can you "kill -QUIT pid" the app first, then send the log file (should be

Neither the app nor MonoDevelop obey kill -QUIT

I attach the log file. Here's what I've done:

- just start fresh MonoDevelop
- start debugging on the simulator
- don't interact with either MooDevelop nor with Simulator
- just wait couple of minutes
- select MonoDevelop window to detect spinning rainbow ball
- kill -QUIT the app process
- kill -QUIT the MD process
- The zipped log is available from
  https://www.dropbox.com/s/bi6we880ir6gbne/MonoDevelop.log.zip

Please do tell me if other stuff is needed to help pinpointing this
problem, anything to solve this...


> ~/Library/Logs/MonoDevelop-3.0/MonoDevelop.log - but it might be different
> if you're using a different MonoDevelop version or if you're running
> multiple MonoDevelop instances at the same time).
>
> Rolf

Rolf's answer:

It looks like MonoDevelop is stuck / very busy printing out logging
information for a (recurring) gtk warning.

I suggest you file a bug for MonoDevelop (http://bugzilla.xamarin.com) with
the log file you provided.

Rolf
Comment 1 guivho 2012-09-13 07:44:46 UTC
Created attachment 2520 [details]
Activity monitor problem report info
Comment 2 guivho 2012-09-13 07:47:19 UTC
Comment on attachment 2520 [details]
Activity monitor problem report info

The title is misleading. This also happens when debugging on the iPhone. Monodvelop starts eating 100% and more of one of the processor cores (I even witnessed a case where Activity Monitor reported 206,7%).

I killed MonoDevelop using the big red button of the Activity Monitor. The resulting problem report window has been captured and is appended in a zip file.

This is not, repeat not a 'normal' problem!

It is just completely impossible to do any debugging!

Please help!
Comment 3 Mikayla Hutchinson [MSFT] 2012-09-13 15:17:12 UTC
It looks like something MD is doing is causing GTK to spew massive amounts of the following warning:
ERROR [2012-08-06 21:32:29Z]: Gtk-Critical: gtk_tree_view_column_set_fixed_width: assertion `fixed_width > 0' failed
Stack trace: 
   at Gtk.TreeViewColumn.set_FixedWidth(Int32 value)
   at MonoDevelop.Debugger.ObjectValueTreeView.AdjustColumnSizes() in /Users/builder/data/lanes/monodevelop-lion-monodevelop-3.0.3-branch/3d53e136/source/monodevelop/main/src/addins/MonoDevelop.Debugger/MonoDevelop.Debugger/ObjectValueTreeView.cs:line 273
   at MonoDevelop.Debugger.ObjectValueTreeView.OnSizeAllocated(Rectangle allocation) in /Users/builder/data/lanes/monodevelop-lion-monodevelop-3.0.3-branch/3d53e136/source/monodevelop/main/src/addins/MonoDevelop.Debugger/MonoDevelop.Debugger/ObjectValueTreeView.cs:line 244
   at Gtk.Widget.sizeallocated_cb(IntPtr widget, IntPtr allocation)
   at Gtk.Widget.gtk_widget_size_allocate(IntPtr , IntPtr )
   at Gtk.Widget.SizeAllocate(Rectangle allocation)
   at MonoDevelop.Components.Docking.CustomFrame.OnSizeAllocated(Rectangle allocation) in /Users/builder/data/lanes/monodevelop-lion-monodevelop-3.0.3-branch/3d53e136/source/monodevelop/main/src/core/MonoDevelop.Ide/MonoDevelop.Components.Docking/DockItemContainer.cs:line 384
   at Gtk.Widget.sizeallocated_cb(IntPtr widget, IntPtr allocation)

I suspect it's logging so much, that it's effectively hanging the rest of MD.
Comment 4 guivho 2012-09-13 15:19:16 UTC
Michael,

Is there some way to tell MonoDevelop either not to log or to be less verbose?

TIA, Guido
Comment 5 Mikayla Hutchinson [MSFT] 2012-09-13 15:22:28 UTC
I'm afraid there isn't, sorry. These errors come from the GUI toolkit library that we use.
Comment 6 Lluis Sanchez 2012-09-20 06:27:23 UTC
I think Jeff committed a fix for this. Jeff, can you confirm?
Comment 7 Jeffrey Stedfast 2012-09-20 10:59:03 UTC
I committed a fix for the gtk warnings, but not sure if it fixes the hang or not.
Comment 8 Len Charest 2012-10-05 18:12:27 UTC
Another data point: I have not had MD freeze on me, but I am seeing the GTK spew in Monodevelop.log. The spew is a serious problem since the GTK messages will continue to be pumped out as long the debugger is active, thereby eventually filling up the disk (this happened to me). Please push out the fix ASAP.

Note that each warning message (i.e., same timestamp) is always printed multiple times, even thousands of times. Here is a snippet of output produced by "grep Gtk-Critical MonoDevelop.log | sort | uniq -c": 

 641 ERROR [2012-10-05 14:47:08Z]: Gtk-Critical: gtk_tree_view_column_set_fixed_width: assertion `fixed_width > 0' failed
1075 ERROR [2012-10-05 14:47:09Z]: Gtk-Critical: gtk_tree_view_column_set_fixed_width: assertion `fixed_width > 0' failed
 852 ERROR [2012-10-05 14:47:10Z]: Gtk-Critical: gtk_tree_view_column_set_fixed_width: assertion `fixed_width > 0' failed
1071 ERROR [2012-10-05 14:47:11Z]: Gtk-Critical: gtk_tree_view_column_set_fixed_width: assertion `fixed_width > 0' failed
 961 ERROR [2012-10-05 14:47:12Z]: Gtk-Critical: gtk_tree_view_column_set_fixed_width: assertion `fixed_width > 0' failed
1127 ERROR [2012-10-05 14:47:13Z]: Gtk-Critical: gtk_tree_view_column_set_fixed_width: assertion `fixed_width > 0' failed
 873 ERROR [2012-10-05 14:47:14Z]: Gtk-Critical: gtk_tree_view_column_set_fixed_width: assertion `fixed_width > 0' failed
1118 ERROR [2012-10-05 14:47:15Z]: Gtk-Critical: gtk_tree_view_column_set_fixed_width: assertion `fixed_width > 0' failed
1012 ERROR [2012-10-05 14:47:16Z]: Gtk-Critical: gtk_tree_view_column_set_fixed_width: assertion `fixed_width > 0' failed
1111 ERROR [2012-10-05 14:47:17Z]: Gtk-Critical: gtk_tree_view_column_set_fixed_width: assertion `fixed_width > 0' failed
1099 ERROR [2012-10-05 14:47:18Z]: Gtk-Critical: gtk_tree_view_column_set_fixed_width: assertion `fixed_width > 0' failed
 988 ERROR [2012-10-05 14:47:19Z]: Gtk-Critical: gtk_tree_view_column_set_fixed_width: assertion `fixed_width > 0' failed


MonoDevelop 3.0.4.7
Installation UUID: 75539609-aebb-4e18-8a86-6b5b51b7b362
Runtime:
	Mono 2.10.9 (tarball)
	GTK 2.24.10
	GTK# (2.12.0.0)
	Package version: 210090011
Apple Developer Tools:
	 Xcode 4.5 (1839)
	 Build 4G182
Monotouch: 6.0.2
Mono for Android: Not Installed

Build information:
	Release ID: 30004007
	Git revision: ea0108260c6a376ecaeffcdb7d03387bd51edda3
	Build date: 2012-09-17 14:09:17+0000
	Xamarin addins: ec43fd5cb223ead4234a9858d1b56eef03dad53a-dirty
Operating System:
	Mac OS X 10.8.2
	Darwin brewer.local 12.2.0 Darwin Kernel Version 12.2.0
	    Sat Aug 25 00:48:52 PDT 2012
	    root:xnu-2050.18.24~1/RELEASE_X86_64 x86_64
Comment 9 Jeffrey Stedfast 2012-10-05 20:23:03 UTC
As a workaround, resize the debugger panes to a larger size.

This can only happen if you've shrunk the debugger panes too small.
Comment 10 Jeffrey Stedfast 2013-01-08 15:33:43 UTC
has anyone had this problem with the newer MonoDevelop releases? e.g. 3.0.6 or 3.1.1?
Comment 11 guivho 2013-01-09 02:56:54 UTC
I just did some tests with 3.0.6 and it seems to work well. Did not
detect this earlier while by now I'm used to debug by console output
of strategic values at strategic places. It's refreshing to experience
that M nowD stays alert while debugging. Will certainly use it more
from now on and would report any problems.
Comment 12 Jeffrey Stedfast 2013-01-09 09:37:45 UTC
thanks for the update!
Comment 13 eImike 2013-01-25 12:02:18 UTC
My debugger hangs with MD 3.1.1 on Mac 10.8.2 
=(.
Comment 14 Jeffrey Stedfast 2013-01-25 12:07:29 UTC
Mike:

Can you try to `kill -QUIT` on the MonoDevelop process and then attach the MonoDevelop log file here? The log file will be in ~/Library/Logs/MonoDevelop-3.0/MonoDevelop.log

Thanks.
Comment 15 eImike 2013-01-25 12:35:15 UTC
Doesn't look think much.

MonoDevelop.log
Starting MonoDevelop
   Loading Workbench
      Initializing Main Window
WARNING [2013-01-25 09:29:13Z]: Subversion addin could not load libsvn_client, so it will be disabled.
WARNING [2013-01-25 09:29:13Z]: First run content index not found.
MacDir exists
Basedir=/Library/Frameworks/Mono.framework/Versions/2.10.9/lib/monodoc
Error: did not find one of the files in sources//Library/Frameworks/Mono.framework/External/monodoc/MonoAndroid-man

AndroidTools.log
[2013-01-25 09:30:42.1] INFO: Starting Android device monitor
[2013-01-25 09:30:45.3] INFO: Adb server launch operation completed
[2013-01-25 09:30:45.3] INFO: Creating android device tracker
[2013-01-25 09:30:45.3] DEBUG: TrackDeviceTask got: 
[2013-01-25 09:30:45.3] INFO: Got new device list from adb
[2013-01-25 09:31:35.1] DEBUG: TrackDeviceTask got: emulator-5554	offline
[2013-01-25 09:31:35.1] INFO: Got new device list from adb
[2013-01-25 09:32:17.3] DEBUG: TrackDeviceTask got: emulator-5554	device
[2013-01-25 09:32:17.3] INFO: Got new device list from adb
[2013-01-25 09:32:17.3] DEBUG: RunShellCommand: emulator-5554 getprop
[2013-01-25 09:33:46.4] DEBUG: TrackDeviceTask got: 
[2013-01-25 09:33:46.4] INFO: Got new device list from adb
[2013-01-25 09:35:28.9] DEBUG: TrackDeviceTask got: emulator-5554	offline
[2013-01-25 09:35:28.9] INFO: Got new device list from adb
[2013-01-25 09:35:46.9] DEBUG: TrackDeviceTask got: emulator-5554	device
[2013-01-25 09:35:46.9] INFO: Got new device list from adb
[2013-01-25 09:35:46.9] DEBUG: RunShellCommand: emulator-5554 getprop
Comment 16 eImike 2013-01-25 13:03:58 UTC
Starting MonoDevelop
   Loading Workbench
      Initializing Main Window
WARNING [2013-01-25 10:22:57Z]: Subversion addin could not load libsvn_client, so it will be disabled.
WARNING [2013-01-25 10:22:57Z]: First run content index not found.
MacDir exists
Basedir=/Library/Frameworks/Mono.framework/Versions/2.10.9/lib/monodoc
Error: did not find one of the files in sources//Library/Frameworks/Mono.framework/External/monodoc/MonoAndroid-man
WARNING [2013-01-25 10:25:33Z]: Failed to clear debug property on device
Mono.AndroidTools.DeviceNotFoundException: Device 'emulator-5554' not found
  at Mono.AndroidTools.Util.AggregateAsyncResult.CheckError (CancellationToken token) [0x00030] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-3.1-series/5d928ec4/source/md-addins/MonoDevelop.MonoDroid/external/androidtools/Mono.AndroidTools/Util/AggregateAsyncResult.cs:72 
  at Mono.AndroidTools.Adb.AdbClient.EndWriteCommandWithStatus (IAsyncResult asyncResult) [0x00007] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-3.1-series/5d928ec4/source/md-addins/MonoDevelop.MonoDroid/external/androidtools/Mono.AndroidTools/Adb/AdbClient.cs:310 
  at Mono.AndroidTools.Adb.AdbClient.ConnectTransport_OnGotTransport (IAsyncResult result) [0x0000c] in /Users/builder/data/lanes/monodevelop-lion-monodevelop-3.1-series/5d928ec4/source/md-addins/MonoDevelop.MonoDroid/external/androidtools/Mono.AndroidTools/Adb/AdbClient.cs:180
Comment 17 eImike 2013-01-25 13:06:01 UTC
[2013-01-25 10:23:24.7] INFO: Starting Android device monitor
[2013-01-25 10:23:24.7] INFO: Adb server launch operation completed
[2013-01-25 10:23:24.7] INFO: Creating android device tracker
[2013-01-25 10:23:24.7] DEBUG: TrackDeviceTask got: emulator-5554	device
[2013-01-25 10:23:24.8] INFO: Got new device list from adb
[2013-01-25 10:23:24.8] DEBUG: RunShellCommand: emulator-5554 getprop
[2013-01-25 10:23:40.4] DEBUG: RunShellCommand: emulator-5554 am broadcast -a mono.android.intent.action.PACKAGE_VERSIONS -e "packages" "Mono.Android.DebugRuntime,Mono.Android.Platform.ApiLevel_15,PufferFish.Application.Android" Mono.Android.DebugRuntime/com.xamarin.mono.android.PackageVersions
[2013-01-25 10:23:52.9] DEBUG: RunShellCommand: emulator-5554 pm uninstall "PufferFish.Application.Android"
[2013-01-25 10:24:01.4] DEBUG: RunShellCommand: emulator-5554 pm install "/data/local/tmp/PufferFish.Application.Android-Signed.apk"
[2013-01-25 10:24:08.3] DEBUG: RunShellCommand: emulator-5554 rm "/data/local/tmp/PufferFish.Application.Android-Signed.apk"
[2013-01-25 10:24:08.4] DEBUG: RunShellCommand: emulator-5554 "pm" "path" "PufferFish.Application.Android"
[2013-01-25 10:24:09.6] DEBUG: Stat: FileInfo for /data/data/PufferFish.Application.Android/files/.__override__: ---------
[2013-01-25 10:24:09.6] DEBUG: RunShellCommand: emulator-5554 setprop "debug.mono.extra" ""
[2013-01-25 10:24:09.6] DEBUG: RunShellCommand: emulator-5554 am start -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -n PufferFish.Application.Android/pufferfish.application.android.SplashActivity
[2013-01-25 10:24:10.9] DEBUG: Stat: 0 FileInfo for /data/data/PufferFish.Application.Android/files/.__override__ : ---------
[2013-01-25 10:24:11.1] DEBUG: Stat: 1 FileInfo for /data/data/PufferFish.Application.Android/files/.__override__ : ---------
[2013-01-25 10:24:11.4] DEBUG: Stat: 2 FileInfo for /data/data/PufferFish.Application.Android/files/.__override__ : drwxrwxrwx
[2013-01-25 10:24:11.4] DEBUG: RunShellCommand: emulator-5554 am broadcast -a mono.android.intent.action.SEPPUKU -c mono.android.intent.category.SEPPUKU.PufferFish.Application.Android PufferFish.Application.Android/mono.android.Seppuku
[2013-01-25 10:24:15.5] DEBUG: NotifyPhase: Enumerating remote files
[2013-01-25 10:24:15.6] DEBUG: NotifyPhase: Determining required operations
[2013-01-25 10:24:15.6] DEBUG: NotifyPhase: Creating directories
[2013-01-25 10:24:15.6] DEBUG: NotifySync: SkipCreateDirectory  /data/data/PufferFish.Application.Android/files/.__override__ 0
[2013-01-25 10:24:15.6] DEBUG: NotifyPhase: Uploading files
[2013-01-25 10:24:15.6] DEBUG: NotifySync: CopyFile /Users/mike.ottiano/Subversion/CornerstoneFramework/Android/Lightwave/PufferFish/PufferFish.Application/PufferFish.Application.Android/bin/Debug/PufferFish.Application.Android.dll /data/data/PufferFish.Application.Android/files/.__override__/PufferFish.Application.Android.dll 8192
[2013-01-25 10:24:15.7] DEBUG: NotifySync: CopyFile /Users/mike.ottiano/Subversion/CornerstoneFramework/Android/Lightwave/PufferFish/PufferFish.Application/PufferFish.Application.Android/bin/Debug/PufferFish.Application.Android.dll.mdb /data/data/PufferFish.Application.Android/files/.__override__/PufferFish.Application.Android.dll.mdb 3923
[2013-01-25 10:24:15.7] DEBUG: NotifyPhase: Upload completed
[2013-01-25 10:24:16.1] DEBUG: KillProcessIfRunningAndWaitForExit: Checking whether app PufferFish.Application.Android is running
[2013-01-25 10:24:16.1] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:16.4] DEBUG: KillProcessIfRunningAndWaitForExit: App was not running, skipping kill
[2013-01-25 10:24:16.4] DEBUG: RunShellCommand: emulator-5554 date +%s
[2013-01-25 10:24:16.5] DEBUG: RunShellCommand: emulator-5554 setprop "debug.mono.extra" "debug=127.0.0.1:8817:8818,timeout=1359134685,loglevel=0,server=y"
[2013-01-25 10:24:16.6] DEBUG: RunShellCommand: emulator-5554 am start -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -n PufferFish.Application.Android/pufferfish.application.android.SplashActivity
[2013-01-25 10:24:19.0] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:19.3] DEBUG: GetLogCat: logcat -v time "dalvikvm:S" "ActivityThread:S" "mkestner:S" "MonoDroid-Debugger:S"
[2013-01-25 10:24:19.3] DEBUG: RunShellCommand: emulator-5554 logcat -v time "dalvikvm:S" "ActivityThread:S" "mkestner:S" "MonoDroid-Debugger:S"
[2013-01-25 10:24:20.3] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:21.4] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:22.5] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:23.6] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:24.7] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:25.9] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:27.0] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:28.2] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:29.3] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:30.4] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:31.4] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:32.5] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:33.5] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:34.6] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:35.6] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:36.7] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:37.8] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:38.8] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:40.0] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:41.0] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:42.1] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:43.1] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:44.2] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:45.3] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:46.4] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:47.5] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:48.7] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:49.8] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:50.9] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:52.0] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:53.4] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:54.6] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:55.6] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:56.7] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:57.7] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:58.8] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:24:59.8] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:00.9] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:02.2] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:03.3] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:04.3] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:05.4] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:06.5] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:07.6] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:08.8] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:09.8] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:10.9] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:12.4] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:13.9] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:14.9] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:16.1] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:17.2] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:18.4] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:19.5] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:20.6] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:21.8] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:22.8] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:23.9] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:24.9] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:26.0] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:27.0] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:28.2] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:29.3] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:30.4] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:31.4] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:32.5] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:33.5] DEBUG: RunShellCommand: emulator-5554 ps
[2013-01-25 10:25:33.9] DEBUG: TrackDeviceTask got: 
[2013-01-25 10:25:33.9] INFO: Got new device list from adb
[2013-01-25 10:25:33.9] DEBUG: RunShellCommand: emulator-5554 setprop "debug.mono.extra" ""
[2013-01-25 10:25:59.2] DEBUG: TrackDeviceTask got: emulator-5554	offline
[2013-01-25 10:25:59.2] INFO: Got new device list from adb
[2013-01-25 10:26:17.2] DEBUG: TrackDeviceTask got: emulator-5554	device
[2013-01-25 10:26:17.2] INFO: Got new device list from adb
[2013-01-25 10:26:17.2] DEBUG: RunShellCommand: emulator-5554 getprop