Investigating the behavior of IOS threads, I wrote a simple torture program to serially create a lot of threads, each thread creates a little garbage and exits. I found that this program rapidly crashes IOS, having run out of memory.
In Nativemethods.m I discovered that the threadsToDelete array fills up, and once full the code in ThreadRunner just drops it if there's no place in the array, which results in permanent leakage of the thread's resources. This ought to be rewritten to use a non-finite resource for the threads pending deletion. If you agree with the diagnosis, I will do that and submit a push. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/a21a933f-3f99-4b50-b09a-ca6be353fd3d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
