Yeah,
well yes, I think it is related to that other post on which the
Socket.Close() is actually creating a complete lock over the app...
Im trying to force a crash of the app if it occurs by having an thread which
give 5 seconds to app to terminate. If not then if called and unsafe DLL to
crash vonlontarely the app...
Found that code on the web
[System.Runtime.InteropServices.DllImport ("libc")]
static extern int strlen (IntPtr zero);
static unsafe void Tick ()
{
int zero = 0;
int* z = &zero;
// This is so that strlen is initialized
// (so no/fewer locks are required later)
strlen ((IntPtr) z);
// The sleep interval can be modified to sleep
// until you're sure the app has hung.
System.Threading.Thread.Sleep (5000);
// Create a crash report
strlen (IntPtr.Zero);
}
Even that could not solve it... I even try to kill the task by using the
on/off and home screen button, but not luck there either... (I guess im not
killing the good process as bug occurs when app is restarted and clearly the
faulty process isnt the new one, it is the previous one that didnt close all
the way thru.)
This one is really challenging...
Jef
--
View this message in context:
http://monotouch.2284126.n4.nabble.com/Black-Screen-of-death-tp4656416p4656463.html
Sent from the MonoTouch mailing list archive at Nabble.com.
_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch
