I'm tracking the IOS UI lockup I reported in another thread long ago, but 
have some new data, because
this time I was running the locked app under the ios simulator.

The EDT thread is marked ->threadBlockedByGC and is waiting at the end of 
monitorEnter.
This accounts for the UI lockup symptom.

The GC thread is waiting in codename1GCMark, waiting for thread 17 to be 
inactive.

Thread 17 doesn't exist.  Its threadData table seems to be in good repair, 
but there
is no thread 17 in allThreads

threadsToDelete is all nulls.

... with my imperfect understanding of the threading and gc environment, it 
looks like
thread 17 went away while the GC was waiting for it, and no one told the GC.

-- 
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/e8221677-ed15-4766-b2e1-7f1ad98bf46b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to