Thanks Richard, I will use sqlite3_memory_used and get back on this thread.
Gperftools was written by google(Sanjay Ghemawat) and is maintained here
https://code.google.com/p/gperftools/ I will check on their support list to see
if this is a known issue.
I have a related question though:-
-my
On Thu, Oct 2, 2014 at 2:21 PM, Mayank Kumar (mayankum)
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.
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. 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
During the running of the fail2ban daemon, which uses python2.7 bindings
for sqlite, the function sqlite3_value_type dereferenced a NULL pointer,
thus causing Segmentation fault error.
Bellow are attached links to stacktraces leading to this segfault ([1]
and more detailed in [2]).
[1]
4 matches
Mail list logo