[codenameone-discussions] Re: New iOS Crash

2017-01-09 Thread Jérémy MARQUER
Thanks. I've managed my implementation so all database access are executed into one thread. ThreadQueue implementation of Steve (https://gist.github.com/shannah/2becc8cf4e23b89ef78f) has helped me. FYI, I've override all methods of Database class ... On Saturday, January 7, 2017 at 7:16:09

[codenameone-discussions] Re: New iOS Crash

2017-01-06 Thread Jérémy MARQUER
I'm pretty sure to close all my cursor in finally close using Util.cleanup(...) method. About the connection of database, It remain open during all life cycle. I think my problem is related to thread. As you mentioned above, SQLite API is not thread safe. I will investigate to wrap this API to

[codenameone-discussions] Re: New iOS Crash

2017-01-05 Thread Shai Almog
Hi, it's the wrong way to think about it... The GC happens. You need to make sure to close connections and cursors when you are done with them. Notice that if you don't the simulator should print warnings to the console too. -- You received this message because you are subscribed to the Google

[codenameone-discussions] Re: New iOS Crash

2017-01-05 Thread Jérémy MARQUER
Hi ! I'm facing a similar issue... How can we avoid GC when a connection or cursor is opened ? How can we improve database access to be threaded-safe ? It's very difficult to avoid crash. Le mardi 25 août 2015 18:21:26 UTC+2, Shai Almog a écrit : > > It had me a bit stumped so I consulted