Hi, not getting it but OOM's are pretty hard to catch normally. I suggest using a profiler on the desktop to make sure you don't have a memory leak in the Java side just to be 100% safe. Normally log output for OOM's isn't exactly helpful but it might provide some details.
Since the crash is portable both to Android and iOS I'm guessing it's somewhere in the Java code which means you should be able to see it on the simulator as constantly growing memory. -- 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/b812dc7d-e2ca-4d5d-b7c3-6bea29571e46%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
