Unfortunately logcat isn't telling me anything. I see
10-22 16:15:57.759 I/ActivityManager( 233): START
{act=android.intent.action.MAIN cat=[android.intent.category.HOME]
flg=0x10000000 cmp=com.android.launcher/com.android.launcher2.Launcher} from
pid 6642
10-22 16:15:57.809 I/ActivityManager( 233): Process
MinefieldManagement.MinefieldManagement (pid 6642) has died.
10-22 16:15:57.809 I/WindowManager( 233): WIN DEATH: Window{415962f8
MinefieldManagement.MinefieldManagement/minefieldmanagement.MainActivity
paused=true}
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Jonathan Pryor
Sent: Monday, October 22, 2012 3:07 PM
To: Discussions related to Mono for Android
Subject: Re: [mono-android] Background thread kills application
On Oct 22, 2012, at 9:47 AM, Jeremy A. Kolb - ARA/NED <[email protected]> wrote:
> I'm running into a weird problem where I have a background thread initiated
> by ThreadPool.QueueUserWorkItem(). If the thread takes too long to execute
How long is "too long"? Which Android version are you seeing this on? Which
target device?
> I just see START and then WIN DEATH.
Usually that's indicative of a crash somewhere. Try looking at logcat directly
instead of using the IDE's Application Output window and see if there are any
unhandled exceptions.
http://docs.xamarin.com/android/advanced_topics/android_debug_log
Thanks,
- Jon
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
