DemiseScythe

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

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.