What looks not related to memory issue is that the crash seems to happen in #close:
Smalltalk stack dump: 0xffc655d4 SqliteLibrary>close: 0x9726108: a(n) SqliteLibrary 0xffc655f4 SQLiteConnection>close 0xc672d08: a(n) SQLiteConnection 0xffc65610 SQLiteConnection>finalize 0xc672d08: a(n) SQLiteConnection 0xffc65630 WeakFinalizerItem>finalizeValues 0xc692b60: a(n) WeakFinalizerItem The idea is obvious...and I did exactly the same for SqueakDBX (now OpenDBXDriver / Garage).... register the connections into the WeakRegistry so that they are automatically closed without having the user to manually do so. I remember I had a case where the user WAS already doing an explicit close and I would crash very much like this case when I was trying to close a connection that was already closed. I don't have Sqlite library handy, but could it be something similar? On Tue, Apr 12, 2016 at 9:49 PM, Offray Vladimir Luna Cárdenas < offray.l...@mutabit.com> wrote: > Hi, > > On 12/04/16 16:51, Stephan Eggermont wrote: > >> On 12/04/16 22:44, Offray Vladimir Luna Cárdenas wrote: >> >>> I'm working with visualizations a external dataset which contains 270k >>> records. So the best strategy seems to bridge pharo with SQLite to keep >>> requirements low while using Roassal to visualize aggregated information >>> that is obtained from querying the database. >>> >> >> It won't fit in image? >> >> > I tried with RTTabTable and NeoCVS but they can not load the data. I made > a test drawing 150k points and the image starts to lag and trying to query > the data becomes inefficient compared to query the data on SQLite. For the > moment I'll export the query results to CVS, but I'll hope to have the > SQLite bridge working soon. > > Offray > > -- Mariano http://marianopeck.wordpress.com
