stack traces are long gone, but were uninteresting. They were all just blocked at the exit of a monitor. The interesting point was that the gc was waiting forever for a process that no longer exists in allThreads
On Sunday, April 30, 2017 at 10:17:20 PM UTC-7, Shai Almog wrote: > > You can copy and paste the stack traces of all the threads in plain text > and file an issue on the deadlock. It's possible there is a race condition > here that we missed. > -- 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/d4f5dca5-94db-46ea-a945-a30d658dd844%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
