Daren
Agreed i found an earlier post. This is just the way
the coding works for the OS posix file locking bug
work around...
I think there is still another memory issue... Not
really a leak, but rather a huge amount of excessive
allocation happening... The sqlite_compile, bind,
reset logic seems to be using more and more memory
each time through the loop, causing the processes
Virtual Memory foot print to grow.
I don't think it should behave this way...Resetting
the VM should release any prior allocated memory ( or
at least mark it as re-usable) It seems to be
allocating additional memory each time through the
loop.
I'm not sure where this is happening ( it could be in
the the bind, step or the reset )...
Again any input is appreciated.
Ken
--- Darren Duncan <[EMAIL PROTECTED]> wrote:
> My interpretation of your results is that you do not
> have a memory leak.
>
> This is partly evidenced that all of the memory in
> the summary is
> "still reachable"; a leak is defined as memory you
> have not freed but
> can not reach.
>
> I also know for a fact that SQLite maintains an
> in-memory cache to
> speed things up, and that is probably why your
> memory usage increased
> over time.
>
> I don't see a problem.
>
> -- Darren Duncan
>
> At 10:11 AM -0700 6/25/04, kenneth long wrote:
> >Hi all,
> >I'm curious if anyone has experience a memory leak
> >with sqlite? Here is the program outline:
> >
> >---- Output:
> >Number of Mallocs: 101882
> >Number of Free : 66747
> >--- Also I ran this through valgrind on linux and
> had
> >the following output...
> >
> >===========================================
> >==3457== LEAK SUMMARY:
> >==3457== definitely lost: 0 bytes in 0 blocks.
> >==3457== possibly lost: 0 bytes in 0 blocks.
> >==3457== still reachable: 53791 bytes in 205
> blocks.
> >==3457== suppressed: 0 bytes in 0 blocks.
> >
> >So, I'm curious if this is "normal and expected
> >behavior" It seems that the program grows pretty
> >rapidly when using the compile/reset methods.. And
> >that the VM memory is being added to each time
> >through the loop.
> >
> >Its starts at rough size of about 2m of Virtual
> Memory
> >and grows to 30M of VM through the execution of the
> >loop. Any ideas on how to reclaim this memory?
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
