The given key '[number]' was not present in the dictionary.

[duerra]

I continue to get this error message in Launchbox.  It doesn't always seem to crash the app, though sometimes it does.  It happens when the app is just running - not necessarily starting, shutting down, during a game launch, switching between platforms, or any other engagement, but I can't seem to get rid of it.  Any ideas?

The given key '185' was not present in the dictionary.

App:     LaunchBox
Version: 13.6
Theme:   Default
Type:    System.Collections.Generic.KeyNotFoundException
Site:    Void ThrowKeyNotFoundException[T](T)
Source:  System.Private.CoreLib

   at Unbroken.LaunchBox.Windows.Desktop.VirtualizingTilePanel.ArrangeOverride(Size finalSize)
   at System.Windows.FrameworkElement.ArrangeCore(Rect finalRect)
   at System.Windows.UIElement.Arrange(Rect finalRect)
   at System.Windows.ContextLayoutManager.UpdateLayout()
   at System.Windows.Interop.HwndSource.Process_WM_SIZE(UIElement rootUIElement, IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam)
   at System.Windows.Interop.HwndSource.LayoutFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   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:

   12:18:12 PM Exception

[duerra]

It's not the same key every time this happens.

Many times, when this happens in happens many, many times in a row, causing exception windows to be rendered across my entire task bar until ultimately Launchbox crashes.

[C-Beats]

This is related to the "Arrange By" feature. Could you let me know what "Arrange By" setting you are using? Also when is this error showing? When you first select a filter, after editing a game, after playing a game? Also what language do you have LaunchBox using? We've tried to replicate this error internally and can't so any additional information you could give would help a lot.

[duerra]

My Arrange By is Date Added.  I can't really identify when the error is showing.  It seems to be at random.  It's not at start or after any identifiable activity.  Typically I'm not even engaging with Launchbox when the error is encountered.  As I mentioned before, sometimes it will result in a crash with endless icons on my task bar, and othertimes it will not crash the app and not cause a bunch of crash icons on my launch bar.  My language is English. 

This error started just a few releases ago.  I had not encountered it prior.

[fromlostdays]

I was getting the same behavior, and same numbered errors. Changing the LB default theme to the old theme seems to have fixed it. To be clear, it's not happening on my main launchbox build. Its only happening on a smaller build I have for hand picked games. The only differences between the two are:

The smaller build obviously has less games imported

I've imported games more recently to the smaller build

The big build is on an M.2 drive (not C Drive); the smaller on a SSD (Also not C Drive)

Lastly, the big build refers to games on a different hard drive (all my games stored seperate), for the smaller build I let launchbox import the the games and store them in LB/Games.

Thats all I can think of. Other than that, same versions of LB, and both were using the newest LB theme until I changed it to the older one on the smaller build. Definitely a puzzle. The first time it happened to me was during an import. And after that, it would usually happen if I tried to scroll games in LB, but not all the time, and it would happen scrolling random systems. 

Edited September 25, 2023 by fromlostdays

[DemiseScythe]

On 9/5/2023 at 9:11 AM, C-Beats said:

This is related to the "Arrange By" feature. Could you let me know what "Arrange By" setting you are using? Also when is this error showing? When you first select a filter, after editing a game, after playing a game? Also what language do you have LaunchBox using? We've tried to replicate this error internally and can't so any additional information you could give would help a lot.

I gave up on this issue for now, for everyone else sort by Title always works without crashing. Maybe because it doesn’t try to do anything fancy.

I thought readding the games I deleted so that all Star Rating categories were populated would fix it and it did for a while, even hiding games or deleting the games again kept it working (dictionary gets rebuilt I guess). Then I tried to go to the next console and it came back. At least I think I understand this bug a little more now.

I use Windows 11, LB, 1080p display, 150% magnification. This results in me only seeing 1 game column when both Side Panel and Game Details are open which I can’t freely resize. Anytime I close one or the other or both, it changes the number of columns visible from 1 to 3. I thought I had fixed this bug for a while but I had the side panel closed and when I opened the side panel, the bug came back so the key must be in the number of columns that appear when I do the sorting to anything other than By Title.

Make a collection with about 100 games, scrape front covers and metadata. 1080p display, 150% scaling. Open both side panel and game details. You should see one game cover per line. Sorted By Title as default. Scroll up and down, it should work. Close side panel to see two columns, scroll up and down, it should work. Sort by Star Rating (first time this happens for this new collection) and scroll up and down, it should work. Open the side panel so number of games per line changes and scroll up and down. You should have your crash and it should keep creating error windows infinitely until Windows decides to kill it. You will see that Title never cares because title doesn’t introduce those category lines that say “1+ Stars” etc. When you open/close panels which is expected behavior, the “dictionary” or whatever you call it, doesn’t refresh/rebuild/update to match the new number of rows like it does when deleting a game and as soon as you start scrolling, it can’t find the same number of rows it used to and crashes.

I added 400+ games, scrape, sorted by Title it works, sorted by Star Rating, it works. That is showing two columns and the details panel. Now I open side panel while still sorted by Star Rating. Now I see only one game column, I grab bar, drag down far enough and crash. 100% reproducible. Interesting enough, it always waits until I get to half the games. Say 400 games, 2 columns, that’s 200 rows. Later, 400 games, 1 column, that’s 400 rows. As soon as I scroll down far enough for it to reach the middle, it crashes because the dictionary has less keys in it. Opening and closing panels should by default update the dictionary. I guess that is why deleting, hiding games didn’t cause issues, it didn’t change the number of columns and by extension rows.

Just for sanity check. Relaunch, sort By Title, close side panel so back to two columns. Scroll, it works. Arrange by Star Rating, scroll, it works. Go back to the top, open side panel so back to 1 column. Arrange by Title, scroll, it works, Arrange by Star Rating (dictionary doesn’t update to the new number of rows like it should automatically do), scroll, it crashes at about half of the bar so just changing it to By Title and back to By Star Rating doesn’t rebuild the dictionary to work with 1 column and twice as many rows. I guess after it first gets sorted/created for that collection, it never bothers to recreate itself? There should be a way to force that so it has twice as many rows.

What happened that first time things got sorted where it decided X game, 2 Columns, need X/2 rows should also happen whenever the number of columns changes which I understand can happen if you resize or snap the window but at the very least, it should be able to detect when the two side panels open and close changing the number of visible columns.

 I’ll check this thread for a while in case you still can’t reproduce it. For everyone else with this issue, change to By Title to avoid the bug, it should work no matter what you do to the viewport.

Edited November 24, 2023 by DemiseScythe

[C-Beats]

On 11/24/2023 at 7:05 AM, DemiseScythe said:

I gave up on this issue for now, for everyone else sort by Title always works without crashing. Maybe because it doesn’t try to do anything fancy.

I thought readding the games I deleted so that all Star Rating categories were populated would fix it and it did for a while, even hiding games or deleting the games again kept it working (dictionary gets rebuilt I guess). Then I tried to go to the next console and it came back. At least I think I understand this bug a little more now.

I use Windows 11, LB, 1080p display, 150% magnification. This results in me only seeing 1 game column when both Side Panel and Game Details are open which I can’t freely resize. Anytime I close one or the other or both, it changes the number of columns visible from 1 to 3. I thought I had fixed this bug for a while but I had the side panel closed and when I opened the side panel, the bug came back so the key must be in the number of columns that appear when I do the sorting to anything other than By Title.

Make a collection with about 100 games, scrape front covers and metadata. 1080p display, 150% scaling. Open both side panel and game details. You should see one game cover per line. Sorted By Title as default. Scroll up and down, it should work. Close side panel to see two columns, scroll up and down, it should work. Sort by Star Rating (first time this happens for this new collection) and scroll up and down, it should work. Open the side panel so number of games per line changes and scroll up and down. You should have your crash and it should keep creating error windows infinitely until Windows decides to kill it. You will see that Title never cares because title doesn’t introduce those category lines that say “1+ Stars” etc. When you open/close panels which is expected behavior, the “dictionary” or whatever you call it, doesn’t refresh/rebuild/update to match the new number of rows like it does when deleting a game and as soon as you start scrolling, it can’t find the same number of rows it used to and crashes.

I added 400+ games, scrape, sorted by Title it works, sorted by Star Rating, it works. That is showing two columns and the details panel. Now I open side panel while still sorted by Star Rating. Now I see only one game column, I grab bar, drag down far enough and crash. 100% reproducible. Interesting enough, it always waits until I get to half the games. Say 400 games, 2 columns, that’s 200 rows. Later, 400 games, 1 column, that’s 400 rows. As soon as I scroll down far enough for it to reach the middle, it crashes because the dictionary has less keys in it. Opening and closing panels should by default update the dictionary. I guess that is why deleting, hiding games didn’t cause issues, it didn’t change the number of columns and by extension rows.

Just for sanity check. Relaunch, sort By Title, close side panel so back to two columns. Scroll, it works. Arrange by Star Rating, scroll, it works. Go back to the top, open side panel so back to 1 column. Arrange by Title, scroll, it works, Arrange by Star Rating (dictionary doesn’t update to the new number of rows like it should automatically do), scroll, it crashes at about half of the bar so just changing it to By Title and back to By Star Rating doesn’t rebuild the dictionary to work with 1 column and twice as many rows. I guess after it first gets sorted/created for that collection, it never bothers to recreate itself? There should be a way to force that so it has twice as many rows.

What happened that first time things got sorted where it decided X game, 2 Columns, need X/2 rows should also happen whenever the number of columns changes which I understand can happen if you resize or snap the window but at the very least, it should be able to detect when the two side panels open and close changing the number of visible columns.

 I’ll check this thread for a while in case you still can’t reproduce it. For everyone else with this issue, change to By Title to avoid the bug, it should work no matter what you do to the viewport.

Thanks for this additional information. I'll sit down and try to replicate again using some of the new details you refer to and see if I can get it to happen.

[C-Beats]

@DemiseScythe Thanks again for the additional information. I WAS able to use it to replicate the issue and will see if I can get it resolved and in the next beta release.

[DemiseScythe]

It sounds good, for now I do 2 columns if I need to Sort by Community Rating.

[C-Beats]

49 minutes ago, DemiseScythe said:

It sounds good, for now I do 2 columns if I need to Sort by Community Rating.

I was able to code changes in place that are currently being reviewed/tested that should correct the issue. I'll do my best to remember to ping ya when they make their way into a beta release so you can try it out and let me know for sure if it resolves the issue.

[C-Beats]

Beta has been pushed that should resolve this issue. Please update and let us know if that is not the case.