[BUG] The process cannot access the file even on "shared" connection

Version .NET 5, LiteDB 5.0.11

Describe the bug The process cannot access the file 'xxx' because it is being used by another process. during Upserts and Deletes in a very heavily used web app.

Too bad, I though LiteDB is thread safe.

Should I maybe create one static instance of db and keep using it throughout the app? Will it be thread-safe then?

Full exception

System.IO.IOException: The process cannot access the file 'xxxx' because it is being used by another process.
   at System.IO.FileStream.ValidateFileHandle(SafeFileHandle fileHandle)
   at System.IO.FileStream.CreateFileOpenHandle(FileMode mode, FileShare share, FileOptions options)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
   at LiteDB.Engine.FileStreamFactory.GetStream(Boolean canWrite, Boolean sequencial)
   at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)
   at System.Lazy`1.ExecutionAndPublication(LazyHelper executionAndPublication, Boolean useDefaultConstructor)
   at System.Lazy`1.CreateValue()
   at LiteDB.Engine.DiskService..ctor(EngineSettings settings, Int32[] memorySegmentSizes)
   at LiteDB.Engine.LiteEngine..ctor(EngineSettings settings)
   at LiteDB.SharedEngine.OpenDatabase()
   at LiteDB.SharedEngine.Delete(String collection, IEnumerable`1 ids)
   at LiteDB.LiteCollection`1.Delete(BsonValue id)

[9600692024]

Hi Team,

LiteDb: 5.0.11 .NET Framework 4.8

I am also facing the same issue, and I can able to fix this issue, by applying the code changes given in https://github.com/mbdavid/LiteDB/issues/1893

When we can expect the next release or patch update for this fix.

[tjmoore]

Still getting this with 5.0.15. Hits certain customers only. Can’t see that they’re on a network share. We store data under %ProgramData% though there’s potential that is on a network share, but our diagnostic logs aren’t showing network drives.

Restarting the services fixes it for a while then happens again and locked out until restarted.