On Feb 20, 2013, at 10:18 AM, Stephan Steiner <stephan.stei...@gmail.com> wrote:
> Is there any reason why this seems to block indefinitely when the app is
> compiled in release mode?
Are you on Android 4.1 Jelly Bean or later? Apparently they disabled the
READ_LOGS permission:
http://stackoverflow.com/questions/11461650/read-logs-permission-on-jelly-bean-api-16
So it looks like logcat access has been removed on newer devices with no
replacement. :-(
> If I use WaitForExit, then after my timeout, p.HasExited is false, and then I
> see my app eating a major amount of CPU time (on my S3 CPU usage is 25% so I
> assume it blocks a single core entirely).
Call p.Kill() after the p.WaitForExit(). That should kill the process if it
hasn't already exited, and on my test device (Nexus 10/Android 4.2.2) there
isn't a `logcat` process executing and consuming tons of CPU.
- Jon
_______________________________________________
Monodroid mailing list
Monodroid@lists.ximian.com
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
