I've noticed a change, starting about the time the IOS build servers were changed over to the current scheme, which appears to be some very low level difference in the treatment of resource loading.
The two symptoms I notice is that loading a resource file in a background thread now seems to cause a complete stall, all processes are frozen, until the load completes. I notice this because at the point the background process is triggered, the UI freezes in a state that's hard to attribute to normal processes. The second symptom is that a load-on-demand scheme for resource images, which can result in the same resource file being reloaded several times, now seems to cause a hard crash. I'm still investigating, but if this description triggers any "aha" or "oh shit" reactions, please share what you can. This affects IOS only. Simulator and Android are not affected. -- 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/774c5749-9726-450f-8e07-e256638df0fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
