Peter McNulty wrote: > > I updated my program to use the latest 1.0.82.0 statically linked binaries for > .net 4.0 and the program quickly developed an unmanaged memory leak, maxing out > the system memory (2gb) in a few seconds. >
There was a behavioral change in how SQLite connections are closed and cleaned up to facilitate better integration with the .NET garbage collector in the 1.0.82.0 release that could partially explain what you are seeing. When a connection is closed, the underlying memory is no longer freed immediately. Instead, it will be freed only after all outstanding statements and backup objects have been finalized. There may be an actual memory leak here; however, that seems unlikely. My first suggestion is to make sure that all commands, data readers, and connections have been closed. There could be cases where the .NET garbage collector might not being aggressive enough. If calling GC.Collect seems to alleviate the issue, that would be a clue. -- Joe Mistachkin _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
