Sorry, should have highlighted this better in my initial message. Started out
using 1.0.56.0 and changed to 1.0.82.0, however problem remains.
________________________________
From: Joe Mistachkin
Sent: 26/09/2012 21:42
To: 'General Discussion of SQLite Database'
Subject: Re: [sqlite] Seemingly random Access Violation errors
Matthew Dumbleton wrote:
>
> at UnsafeNativeMethods.sqlite3_close_interop(IntPtr db)
> at SQLiteBase.CloseConnection(SQLiteConnectionHandle db)
> at SQLiteConnectionHandle.ReleaseHandle()
> at CriticalHandle.Cleanup()
> at CriticalHandle.Dispose(Boolean disposing)
> at CriticalHandle.Dispose()
> at SQLite3.Close()
> at SQLiteConnection.Close()
>
> Yes. Each time either thread connects a new sqliteconnection instance is
created.
> I use a mutex protected static method through which both threads do their
database
> connections in order to ensure database is accessed by only one thread at
a time.
>
I just noticed that the method signature for CloseConnection in the above
stack trace
is outdated. The most recent versions have the following signature:
internal static void CloseConnection(SQLiteConnectionHandle hdl,
IntPtr db)
Could you please try using the latest release version (1.0.82.0) or the
latest code
in trunk and see if that clears the issue.
--
Joe Mistachkin
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
