- changed status to resolved
Crash after exiting game in launchbox
After upgrading to launchbox 10.14 this error has come up several times when exiting a game in launchbox. the error from launchbox is pasted below.
the process cannot access the file 'E:\mame\cfg\silkworm.cfg' because it is being used by another process.
App: LaunchBox
Version: 10.14
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, Boolean useLongPath, Boolean checkHost)
at System.IO.StreamReader..ctor(String path, Encoding encoding, Boolean detectEncodingFromByteOrderMarks, Int32 bufferSize, Boolean checkHost)
at System.IO.File.InternalReadAllText(String path, Encoding encoding, Boolean checkHost)
at (String , String )
at Unbroken.LaunchBox.Windows.Integrations.MameHighScores.EnsureNoDipSwitchChanges(String romFile, String mamePath)
at (<>c__DisplayClass12_0 )
at Unbroken.LaunchBox.Windows.Integrations.MameHighScores.<>c__DisplayClass12_0.<Prepare>b__0()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
Recent Log:
10:23:10 AM Exception
Comments (1)
-
repo owner - Log in to comment
Hi Rich, this issue has already been fixed in the latest beta.