Launchbox Crashing Issue

Issue #7705 open
Luis Gonzalez created an issue

The version of launchbox that I am using is 13.2. I am using a Windows 10 64-bit Operating System. This issue occurs almost every time I attempt to use or modify my launchbox setup. The crash appears to be random. I can be deleting roms, trying to run a rom or attempting to add custom art to my setup and the error occurs.

Here is the error code I receive following by a complete crash.

The process cannot access the file 'D:\Dropbox\LaunchBox\Metadata\Temp\e4a49be7-5df4-47d2-93d1-8cd3809a4256' because it is being used by another process.

App: LaunchBox
Version: 13.2
Type: System.IO.IOException
Site: Void InvokeRemoteFactory(System.Object, System.Object)
Source: Unbroken.LaunchBox.Windows

at Unbroken.LaunchBox.Windows.Data.DataManager.InvokeRemoteFactory(Object init, Object result)
at CreatorInfoWrapper.RateMetaServer(DataSet init, String result, CreatorInfoWrapper )
at Unbroken.LaunchBox.Windows.Data.DataManager.UpdateRemoteFactory(String info)
at InitializerRuleWrapper.RateMetaServer(Object , String info, InitializerRuleWrapper )
at Unbroken.LaunchBox.Windows.Data.DataManager.<>c__DisplayClass171_0.CalculateRemoteObject()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.ThreadHelper.ThreadStart()

Recent Log:

5:28:58 PM Exception

I will point out that this is first time that I’ve attempted to run launchbox from within dropbox. Dropbox is run from my secondary 4 tb D:\ hard drive where the Operating System is not present; the OS is run from my primary C:\ hard drive. If I am unable to fix this, I may consider reinstalling my setup back onto my C:\ hard drive. Thank you. Despite these errors, I love launchbox and I am paid subscriber. Thank you and everyone a part of this project for putting this together.

Comments (3)

  1. brian

    Looks like Dropbox is locking files that LaunchBox needs to access. Any syncing program will do this as they attempt to upload these files to the cloud. It is always recommended not to place LaunchBox in a folder that is being actively used by another program (like Dropbox), as you end up having two programs trying to use the same files.

  2. Danny Nilsson

    it could also be that when Launchbox starts, it creates som symlinks in the install directory. and remove them again when it closed.

  3. Log in to comment