On Tue, Sep 22, 2015 at 12:47 AM, Shuhrat Rahimov <sandrorkmv at gmail.com> wrote:
> thanks for the hint. I've tried with SQLITE_ENABLE_MEMORY_MANAGEMENT to > call sqlite3_release_memory() each time after sqlite3_step(). The memory > usage is different during the whole runtime of the device. At the beginning > it is 80 K and each time the released memory ranges from 0 to 1,7 K, only > once or twice 3,5 K was released. the highest memory usage was 86 K. But > anyway, despite of memory release, each time after power up there can be > executed only 450-500 inserts, then NOMEM is returned, but SQLite memory > usage at that time is only 82 K. Maybe the memory is wasted for other > things and is not released properly. Any hints to this problem would be > very appreciated. > Kind Regards > I've never used them myself, but you may want to look into using the SQLITE_ENABLE_MEMSYS3 or SQLITE_ENABLE_MEMSYS5 options. https://www.sqlite.org/malloc.html might be a good place to start. > > 2015-09-21 14:42 GMT+02:00 Richard Hipp <drh at sqlite.org>: > > > On 9/21/15, Shuhrat Rahimov <sandrorkmv at gmail.com> wrote: > > > What could I do here in order to free > > > memory after sqlite3_step() for further operations. > > > > https://www.sqlite.org/c3ref/db_release_memory.html > > > > -- > > D. Richard Hipp > > drh at sqlite.org > > _______________________________________________ > > sqlite-users mailing list > > sqlite-users at mailinglists.sqlite.org > > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > > > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > -- Scott Robison
