System.Data.SQLite

SQLiteStatement is an IDisposable class. In one particular method it is being created but not disposed. This could lead to potential memory leak.

Call stack of allocation is:

System.Data.SQLite!System.Data.SQLite.SQLite3.Prepare( SQLiteConnection,string,SQLiteStatement,uint,ref string )
System.Data.SQLite!System.Data.SQLite.SQLiteCommand.BuildNextCommand()
System.Data.SQLite!System.Data.SQLite.SQLiteCommand.GetStatement( int )
System.Data.SQLite!System.Data.SQLite.SQLiteDataReader.NextResult()
System.Data.SQLite!System.Data.SQLite.SQLiteDataReader..ctor( SQLiteCommand,CommandBehavior )

Here is NextResult method, the statement is created, but never disposed afterwards.

First, this does not appear to be an actual leak.  The NextResult method does not
create the SQLiteStatement objects (i.e. they are held by the SQLiteCommand
object).

Second, the SQLiteStatement is basically a wrapper for a SQLiteStatementHandle
and the test suite (in the debug build) always counts the number of outstanding
instances of that class (i.e. which should be zero when cleanup is complete).

Given these facts, it seems highly unlikely there is a leak here; however, if you
can demonstrate a leak with C#, I'll be happy to look into it further.

Without further information, this ticket will be closed on November 21st, 2014.