On Thu, Oct 2, 2014 at 2:21 PM, Mayank Kumar (mayankum) <mayan...@cisco.com>
wrote:

> Hi All
> I am using sqlite 3.7.7.1
>
> When profiling my application using gperftools-2.0, the profile always
> shows sqlite3_memory_used as the top user of memory.


My first guess:  A bug in gperftools-2.0.  I'm not familiar with that
tool.  Is it reliable?




> Why would sqlite3_memory_used use so much memory as it just reports the
> status of sqlite3_malloc/free. Are there known memory leaks in this call
> which have been fixed?
>

There have been no known memory leaks in SQLite for a very long time.


>
> Is there a way to just profile the sqlite3 calls to figure out if there is
> a leak in those calls or wrt how I may be using it?
>

Keep calling sqlie3_memory_used() and see if the value keeps going up?


>
> -Mayank
>
>
>
>
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>



-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to