Launchbox crashes / hangs with too many platforms.

[-McFly-]

I'm continually seeing my Bigbox setup hang or crash when I run all my platforms and playlists. I'm trying to use Attract Mode with the Aeon MQ7 theme with almost 800 platforms and a little over 700 playlists. (I have too many and I'm asking too much, I know.)  I've spent the last few weeks going through my hardware, software, operating system, drivers and more with fixes, trial runs, tests, VLC/FFME/Media Player trials, and just about everything I can with AI without success. The final result is to send this to the Launchbox devs, which I'm doing here. Others may have similar issues or have comments to add as well as a few 'just use less platforms and playlists you muppet' which I do, but I'd really like to have this run for more than 90 or so minutes before crashing or freezing with everything added. I've attached a Crash Packet that ChatGPT put together for me and there is a link to other files available inside the document for Devs or anyone else to look at.

Don't get me wrong - I'm not complaining that Bigbox has any errors or should support something this ridiculous, but I really would love to have this running during the day while I sit working from home, for me to look up to and break the monotony that is emails and teams meetings and phone calls and powerpoint presentations. I expect that I'm just asking for too much... but if you don't ask, you don't get...?

BigBox_Developer_Crash_Packet_Mcfly.docx

[-McFly-]

So... I've had it running now for over 3 hours without crashing. Here's what I found.

BigBox was running under PageHeap / IFEO debug instrumentation, which was making it far more likely to terminate or behave abnormally during long runs. Windows had a hidden per-app debugging setting attached to BigBox.exe, even though normal verifier /query looked clean.

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\BigBox.exe
GlobalFlag 0x02000000
PageHeapFlags 0x3

BigBox itself was being destabilized by PageHeap being enabled, and removing it fixed the problem. The crash problem was caused, or at least heavily triggered, by hidden Windows PageHeap debugging being enabled specifically for BigBox.exe.

- This may return or may not have fixed everything but I've not had it run for 3 hours for at least a month.

[JoeViking245]

5 hours ago, -McFly- said:

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\BigBox.exe

What version of Windows are you on?  My Windows 11 doesn't have BigBox.exe in this path.  I'd have to check my cab (which is on W10) to see if it's there.

[-McFly-]

Win 11 24H2 Build 26100.8037

[JoeViking245]

32 minutes ago, -McFly- said:

Win 11 24H2 Build 26100.8037

Mine's Win11 Home 25H2 Build 26200.89037   Don't know if the version/builds are different because mine's the "Home" edition.

[-McFly-]

12 minutes ago, JoeViking245 said:

Mine's Win11 Home 25H2 Build 26200.89037   Don't know if the version/builds are different because mine's the "Home" edition.

Mine's Pro. I went back to an earlier build during the debugging as we went down the graphics card rabbit hole. I'll probably leave it here though.