Fursphere

I'll get some numbers / screenshots for you later today. I'll fire up the cabinets in a minute. Lets say - 'idle' Win11 on a fresh boot is consuming like.. 6gb of memory (or something). I fire up BigBox and just let it run in attract mode for hours. After like.. 6 hours, system has 11gb of memory consumed (11gb/16gb). I shut down BigBox, return to Windows. Task Manager still shows like 10gb/16gb used. That's a memory leak in my book - something is using memory and not properly releasing it. There is probably a tool I can get to 'see' it (raw memory usage). Maybe. This happens on both of my cabinets / BigBox installs. If I boot up the PC and launch HyperSpin 2.0 instead (I've got a startup menu...), this doesn't happen. Doesn't happen with Launchbox.exe either. Just BigBox. Anyway, let me see what I can dig up to support this.

Beta-2 BigBox Memory Leak is not fixed. Still gobbles up gigabytes of memory and never gives it back. (even after closing BigBox - requires a full reboot to clear out) I ran the updated VLC media player for a couple of hours without issue. No crashes or anything.

Any updates on that memory leak issue?

Beta-1 appears to have a nasty memory leak. After 5-6 hours of attract mode, I'm seeing my systems run out of memory and crash. (16gb total system memory)

ON the cabinet I switched to FFMpeg - BigBox did crash out after a couple of hours. So its not just you. I'm not sure of the exact time, because I wasn't paying close attention to it. But it absolutely crashed to the desktop with no error message on the screen. Other cabinet running WMP was still cruising along in attract mode.

@faeran On the shutdown routine. This is a long standing bug / backdoor feature request, but since you're working on the shutdown code base right now anyway.... My twin driving cabinets use Ultimarc PAC-Drives for lighting up LEDs. These are latching - meaning if they are ON when the PC shuts down, they STAY ON (as long as they have power of course). So on those machines, I have to EXIT BigBox, wait for BigBox to fire the LEDBLinky "exit frontend" routine (turn off the LEDs), then gracefully shutdown Windows. If I use the BigBox built in shutdown routine - It doesn't seem to fire the LEDLlinky "frontend exit" routine, and the LEDs (buttons) stay on, even after the PC powers off. So the ask if you can work it in - Can you add the "LEDBlinky Frontend EXIT" routine to the BigBox shutdown routine and make sure it fires BEFORE it starts the Windows Shutdown commands?

@JaredN Doesn't address your issue, but I let my cabinet run on WMP mode yesterday for 12+ hours in attract mode without issue. I can switch one of mine to FFMPEG and see if it crashes. See if its application code, or environmental based (your windows install vs. my windows install, for example).

Ok. I believe you. My solution was to just buy bigger drives and unzip everything at rest (that needed to be unzipped). And trim my collection to remove all the garbage. (terrabytes of bad stuff... lol)

The 'bug' is that the plugin has not been updated for the newer versions of .NET. There is nothing wrong with LB/BB itself. There are a couple of project forks that have been updated to run with the newer versions of launchbox. You should check them out. (github --> insights --> forks) https://github.com/fraganator/archive-cache-manager

The new shutdown routine is pretty cool. Nice touch. Both of my upright cabinets have been updated to the beta and are running good so far.

Got tired of waiting for this to be an official feature, so I vibe coded a plugin.

BigBox Trackball & Spinner Wheel Support View File Trackball & Spinner Support for BigBox Navigation. Supports X & Y axis (configurable) to simulate up/down/left/right menu movement. Option menu support to configure speeds and behavior. Its not perfect, but it does work pretty well. It disables itself when a game is launched. If there is interest in the source, I can put it up on github or something. Just ask. Submitter Fursphere Submitted 05/29/2026 Category Third-party Apps and Plugins  

That's my point though. <open source software> + <the internet> = you can't stop the signal This is why there are fifty-seven-hundred-thousand linux distributions. Someone does something someone else doesn't like (and discussions fail - if they're even attempted) and the whole project is forked. Sometimes soft, sometimes hard. Its the equivalent of "I'm taking my ball and going home". Or getting pissed off at the the state of the board game and flipping the table. "I can't even with these people anymore!" This is awesome in the sense that you can't stop someone for doing whatever they want. This is horrible in the sense that it lets people do whatever they want. lol Linux's worst enemy is not Windows. Its the Linux community.