On Thu, Mar 13, 2014 at 2:57 PM, Eduardo Morras <[email protected]> wrote:
> > Hi, I get app crash if sqlite3_db_release_memory(db) is called and Sqlite3 > has no memory to release, for example calling it twice. > > The backtrace is: > > #0 0x000000000042ab60 in sqlite3PcacheShrink (pCache=0x6f6c6f63207b2065) > at /usr/home/gowen/clang/scgi/src/sqlite3.c:37835 > #1 0x0000000000415f3c in sqlite3PagerShrink (pPager=0x801072308) > at /usr/home/gowen/clang/scgi/src/sqlite3.c:42949 > #2 0x0000000000415ee8 in sqlite3_db_release_memory (db=0x801007808) > at /usr/home/gowen/clang/scgi/src/sqlite3.c:120647 > #3 0x00000000004ab3e3 in db_get_binary_content (fn=0x7fffffffcf10 > "background.jpeg", > size=0x7fffffffce4c, ret=0x7fffffffd6e8) at > /usr/home/gowen/clang/scgi/src/db.c:116 > > Line 116 on #3 is the call to sqlite3_db_release_memory(db). > > I know it's an internal sqlite3 call and I should use > sqlite3_release_memory instead. > sqlite3_db_release_memory() is a valid API that anybody can call. It should just work. We are unable to reproduce your crash. Perhaps there is heap corruption caused by some other part of the application and that this is tripping up SQLite. > > Versions tried 3.8.3, 3.8.4, 3.8.4.1. amalgamation under FreeBSD 9.2 > x86_64. using clang 3.4 compiler. > > --- --- > Eduardo Morras <[email protected]> > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
