Whether and how you can do so will depend on what operating system you are using.
On 27 October 2013 16:10, Raheel Gupta <raheel...@gmail.com> wrote: > Hi, > > Yes, I tried Valgrind and it shows no leaks. > But why would this happen with 64K pages ? In 1024 Sqlite is able to > release all the memory. > > >> It might also be that your memory allocator is holding onto freed memory > rather than releasing it back to the OS. > > How should I free it ? > > > > On Sun, Oct 27, 2013 at 9:46 AM, Richard Hipp <d...@sqlite.org> wrote: > > > On Sun, Oct 27, 2013 at 12:02 AM, Raheel Gupta <raheel...@gmail.com> > > wrote: > > > > > Hi, > > > > > > Sir, if you see my first email, I have already tried that. When the 15 > > > Million records are being outputted, the ram usage shoots to a MAX of > > > 126MB. After the "PRAGMA shrink_memory" it goes down to 65Mb but doesnt > > go > > > below that. > > > > > > > > It might also be that your memory allocator is holding onto freed memory > > rather than releasing it back to the OS. Have you tried running with > > valgrind to see it shows any leaks? > > > > -- > > D. Richard Hipp > > d...@sqlite.org > > _______________________________________________ > > sqlite-users mailing list > > sqlite-users@sqlite.org > > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Christopher Vance _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
