I've only seen this with the Left Behind disc in #32 . This is the error I get
Calculating disk content hash...
Unhandled exception: System.IO.IOException: The process cannot access the file 'C:\Users\user\OneDrive\Documents\Repos\thediscdb-data\data\movie\Left Behind (2014)\f\disc01.txt' because it is being used by another process.
at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode)
at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode)
at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize, Nullable`1 unixCreateMode)
at System.IO.StreamReader.ValidateArgsAndOpenPath(String path, Encoding encoding, Int32 bufferSize)
at System.IO.File.ReadAllLines(String path, Encoding encoding)
at ImportBuddy.DiskContentHash.TryAppendHashInfo(IFileSystem fileSystem, String logFile, DiscHashInfo hashInfo, CancellationToken cancellationToken) in D:\a\data\data\tools\ImportBuddy\source\ImportBuddy\ImportBuddy\DiskContentHash.cs:line 88
at ImportBuddy.ImportTask.ExecuteAsync(CancellationToken cancellationToken) in D:\a\data\data\tools\ImportBuddy\source\ImportBuddy\ImportBuddy\Import\ImportTask.cs:line 326
at ImportBuddy.Shell.RunAsync(CancellationTokenSource cancellationTokenSource) in D:\a\data\data\tools\ImportBuddy\source\ImportBuddy\ImportBuddy\Shell.cs:line 29
at Program.<>c__DisplayClass0_0.<<<Main>$>b__1>d.MoveNext() in D:\a\data\data\tools\ImportBuddy\source\ImportBuddy\ImportBuddy\Program.cs:line 39
--- End of stack trace from previous location ---
at System.CommandLine.Invocation.AnonymousCommandHandler.InvokeAsync(InvocationContext context)
at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass17_0.<<UseParseErrorReporting>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass12_0.<<UseHelp>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<<UseVersionOption>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass19_0.<<UseTypoCorrections>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseSuggestDirective>b__18_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass16_0.<<UseParseDirective>b__0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<RegisterWithDotnetSuggest>b__5_0>d.MoveNext()
--- End of stack trace from previous location ---
at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass8_0.<<UseExceptionHandler>b__0>d.MoveNext()
That error is almost always caused by java.exe holding onto the log file. I'll see if there is a cross-platform way to kill the java process when this happens.
OS: Windows 11 Drive: LG WH16NS40
I've only seen this with the Left Behind disc in #32 . This is the error I get