Hi, I also have a "Maximum number of transactions is reached." issue on my project with versions 5.0.18 & 5.0.19! Do I need to adapt my code in some way?

Note: version 5.0.17 works fine for me too.

This problem occurs even in the case of a single thread.
It is reproduced in the following code:

static void Main()
{
    // Create a new database.
    using var database = new LiteDatabase("test.db");

    var collection = database.GetCollection("test");
    collection.Insert(new BsonDocument { ["_id"] = 1 });

    for (int i = 0; i < 101; i++)
    {
        try
        {
            collection.FindById(1);
        }
        catch (LiteException ex)
        {
            // An exception is thrown when i reaches 100.
            Console.WriteLine(ex.Message);
        }
    }
}

I will send a pull request to fix it.

@mbdavid Assuming this fix has been tested and verified, can we get a new release that includes it?

Note that we rolled this fix into 5.0.19 and found that it resolves the "Maximum number of transactions reached" error, and also the DiskWriterQueue locking issue #2307 which has been preventing us from upgrading to v5.

Hi - what's the update on this? I see a PR linked as open. It would be good to get this issue fixed so we can update.

I saw the same issue when upgrading from 5.0.12 to 5.0.19. Version 5.0.17 is the only workable solution for now it seems...

Hi together, are there any updates on this? Also still staying with 5.0.17 due to this issue