On Apr 14, 2019, at 10:18 PM, David Ashman - Zone 7 Engineering, LLC <[email protected]> wrote: > > It appears that there is a leak somewhere.
It is certainly in your code. My bet’s on a missing sqlite3_finalize() call, but there are many other possibilities. > Does anyone know why this error occurs? I suggest you cross-compile your application, or at least its SQLite-using core, to a real OS and use its memory tracking tools to debug your use of SQLite, then apply that to the embedded app. I’m talking about things like Valgrind, the Google AddressSanitizer now built into GCC and Clang, etc. > Do I have to periodically call the release memory functions No, you have to pair each function that makes allocations (e.g. sqlite3_prepare()) with a call to free that memory (e.g. sqlite3_finalize()). > or is that inherent to SQLite? This is C. There is no inherent memory cleanup. It’s all on you, the programmer. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
