Re: [sqlite] Handle leak using IIS on windows 7?

This was exactly the problem; I didn't realize the 'static' variables are persisted between page views in ASP.Net Adding an '_instance = null;' fixed the issue. Thanks muchly. Cheers, Doug. On Tue, Jul 19, 2011 at 11:58 AM, Joe Mistachkin wrote: > > After reading the

Re: [sqlite] Handle leak using IIS on windows 7?

After reading the code, I noticed the following: 1. From the static Dump method, an instance of the DbLogger class is created via the static Get method and stored in the _instance static variable. 2. The connection itself is opened in the constructor for the DbLogger class via the InitDb

Re: [sqlite] Handle leak using IIS on windows 7?

On 19 Jul 2011, at 4:07am, Doug wrote: > I'm pretty sure the issue is something to do with file handles. For the same > reason after loading the page (from an IIS server) and then closing the > page, waiting 1 minute or two and then attempting to remove the db.sqlite > file, I get an "error,

Re: [sqlite] Handle leak using IIS on windows 7?

Hm... I'm not doing anything fancy. I've attached the tiny sqlite logging class below. It's called in an MVC app simply by invoking: @Html.Raw(Doug.Utils.Web.DbLogger.Dump()) Yes, it uses transactions; is that a bad thing? I'm pretty sure the issue is something to do with file handles. For the

Re: [sqlite] Handle leak using IIS on windows 7?

If you showed a small sample code that caused your problem it would sure help a lot. I peeked at the library code. That message is generated when _cnn is null (the DB connection). private void InitializeForReader() { if (_activeReader != null && _activeReader.IsAlive)