Index was outside the bounds of the array

Issue #7433 new
Jason Parisi created an issue

Hello. Hopefully, I am reporting this error correctly. I was importing a full set of MAME Roms and letting it run to download all the media. The process to get media from EmuMovies was taking a very long time and I was already on day 3 of leaving Launchbox running the whole time. I decided to try and add a few games for the NES while it was still downloading the MAME media. First I got an error that said something like “source array was not long enough” (Sorry I didn’t think to capture it and just hit ok to move on). After that, I got this other error which had a report button that led me here. Below is the copy/pasted error as well as an attached screenshot. Hopefully, you find this helpful. Please let me know if there is anything else you need. Thank you.

“Index was outside the bounds of the array.

App: LaunchBox
Version: 13.0
Type: System.IndexOutOfRangeException
Site: T get_Item(Int32)
Source: System.Private.CoreLib

at System.Collections.Generic.List1.get_Item(Int32 index) at System.Linq.Enumerable.WhereListIterator1.ToArray()
at System.Linq.Buffer1..ctor(IEnumerable1 source)
at System.Linq.OrderedEnumerable1.ToList() at Unbroken.LaunchBox.Windows.Processes.BulkImageDownloader.ProcessQueue(Func1 getIsCancelled, String activeImageGroup, Action2 onIndeterminateUpdate, Action4 onUpdateAction, Action`2 onGameImageDownloaded)
at Unbroken.LaunchBox.Windows.Desktop.ImageDownloaderHelp.<>c.SortReflectiveInterpreter()
at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.RegisterAdvisableResolver(Object )
at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.ValidatePreparedBridge()
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:

10:44:24 PM Exception”

Comments (0)

  1. Log in to comment