Hello René, I've seen this once. The issue (not an easy one to diagnose) was that the application ran out of memory inside the Mono runtime [1]. It could be different, since many (uncommon but possible) errors will lead to the same exception, but that's the most likely condition I can think of.
If this the case then using the thread pool would have the advantage of reusing the same threads (and memory) so this can help (as much as anything that can lower the memory requirements). Sebastien [1] https://github.com/mono/mono/blob/master/mono/metadata/threads.c#L729 On Fri, Apr 20, 2012 at 2:05 PM, René Ruppert <[email protected]> wrote: > Hi, > > > > users report this exception (device iPad 2, DEBUG build): > System.ExecutionEngineException: Couldn't create thread > > > > No stack trace, nothing. I’m not creating (many) threads. From the logs I > can see that it happened while it was running a progress dialog. This means > I spawned _one_ thread but in the middle of its execution it got hit by the > exception above. So it wasn’t me creating another thread. > > For information: The progress threads I use are not created from the Thread > pool but user new Thread(). But only one at a time is running. > > Does anybody have a clue what could cause this? I doubt it is my fault, > looks like something internal. > > Maybe someon from Xamarin can have a look at the sources and find out what > is causing this exception? > > > > René > > > > > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch > _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
