update error

Issue #3698 new
GTAsoldier created an issue

The process cannot access the file 'C:\Users\archv\OneDrive\LaunchBox\Themes\Default\Styles\ThumbnailListBoxStyle.xaml' because it is being used by another process.

App: Big Box Version: 7.16 Type: System.IO.IOException Site: Void WinIOError(Int32, System.String) Source: mscorlib

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode) at (String , String ) at Unbroken.LaunchBox.Wpf.BigBox.App.LoadThemeStyle(String name, String theme) at (String ) at Unbroken.LaunchBox.Wpf.BigBox.App.LoadThemeStyles(String theme) at (Type ) at Unbroken.LaunchBox.Wpf.BigBox.Bootstrapper.GetOrCreateViewType(Type viewType) at Caliburn.Micro.ViewLocator.<>c.<.cctor>b__10_8(Object model, DependencyObject displayLocation, Object context) at Caliburn.Micro.WindowManager.CreateWindow(Object rootModel, Boolean isDialog, Object context, IDictionary2 settings) at Caliburn.Micro.WindowManager.ShowWindow(Object rootModel, Object context, IDictionary2 settings) at (Bootstrapper , Object , StartupEventArgs ) at Unbroken.LaunchBox.Wpf.BigBox.Bootstrapper.OnStartup(Object sender, StartupEventArgs e) at System.Windows.Application.OnStartup(StartupEventArgs e) at System.Windows.Application.<.ctor>b__1_0(Object unused) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Recent Log:

3:09:14 PM Exception

Comments (0)

  1. Log in to comment