flighty

Issue found! Options > Visuals > Boxes > Dynamic Box Sizing = true When it's unchecked, the issue *rarely* happens, rather than literally every time, predictably. Scrolling up is still very hazardous in the "All" category, buy hey, I can actually use Launchbox again.

13.26 seems to have slightly improved performance, even making some previously troublesome platforms fairly safe to scroll, but the "All" category remains nearly unusable. This makes me wonder if Launchbox is trying to load a percentage of the list into VRAM or something- as in a much larger amount of media than is currently onscreen at any one time, and significantly more of a large list than a small one. I have no theories as to why scrolling up seems to accelerate the issue much faster than scrolling down.

I tried everything I could think of, gave up, downloaded and installed a fresh copy of Launchbox 13.25, and began re-importing my library. I got my roms and their metadata and box art imported, then a fair way into my Steam Library (many hours wasted at this point) when the new installation started locking up just like the previous version. There has been no crash, I have not added any plugins, I am doing nothing but entering missing metadata and images. This never happened on the older versions of Launchbox. After more testing, there seems to be some wild inefficiency or leak going on. For context: Windows 11 Home 25H2, AMD Ryzen 9 7950X, 64GB (4 x 16GB) DDR5 RAM, Intel Arc B580 12GB GPU, and Launchbox is running off its own dedicated Samsung 1TB NVME drive. Normal desktop usage (such using this forum, or browsing social media) will show between 0-3% CPU average usage, and 0-8% average GPU usage, 8% spikes being media-heavy doomscrolling. Here's a screenshot of what my Task Manager is showing after just seconds of scrolling my Launchbox library, up to where it locks up entirely (web browser closed, No music, no videos, only scrolling 2D box-fronts): (The sharp drop-off from 100% is Launchbox freezing) I've also noticed that Launchbox will freeze up much faster when scrolling up, even when scrolling very slowly, while it usually takes a while when scrolling down unless I'm scrolling very quickly.

As the title says- Launchbox (but not Bigbox) is almost entirely freezing after a short amount of scrolling through games in at least a couple platform categories. If I click a different category, Launchbox will stay frozen for about another minute before switching to it, and then everything suddenly runs normally unless I go back the the problem category and scroll again. I'm assuming something got corrupted within these categories, but I don't know what to look for. Things I've tried while attempting to troubleshoot: Deleting my current theme, installing and using "Airy" Reinstalling overtop of my current installation Tools > Download > Update Metadata for All Games Removing all music, manuals, videos, and images from my entire library, then downloaded only Box Front images Deleting all music and manual file paths from game metadata from the problematic categories Removed all custom sort titles from my entire library Checking the log file to see what Launchbox is doing while it is freezing up. (It's possible there's something helpful there, but I'm not seeing anything suspicious) Switching between WMP and FFmpeg video playback. Yes, I removed all media, but the log suggested that Launchbox was still looking for media to play, so I tried this just in case. Batch-converted all of the Box Front images into .jpg no larger than 900 x 900 Windows Settings > System > Storage > Temporary files > "Remove files" Admin Command Prompt "sfc /SCANNOW" and "DISM /Online /Cleanup-Image /RestoreHealth" Win + R > "msdt.exe -id DeviceDiagnostic" What should my next steps be? This is has been going on for months and I don't have a trustworthy data backup to attempt to restore without rolling back a very very long time, so I would like to try other solutions first, if anyone has any ideas other than starting completely fresh? (None of this was at all helpful. See my reply below for more details about the issue.)