megashub

2nd attempt to capture details about the progression of this problem: 12:55 start progressed exactly the same as first attempt 2:01 was the last time the clock updated. 2:20 all video and images stopped displaying almost entirely. Every third or fourth game, the video appears and plays, sometimes only for a second or two. Only the text title information is reliable and keeps changing with every spin. 2:47 CTD

10:19 start 10:23 slight jitters noticed toward the end of the spin 10:33 jitters still slightly noticeable, a few more, but still very slight. Only apparent on the longer-duration spins where max spin speed is achieved. Noticing on the long-duration spins that when the wheel is spinning at its fastest, only a small subset of logos are being rotated and displayed. Though the game selection itself does still seem to involve the whole game list. At the beginning when Attract Mode first started, the high speed logo spin appeared to include a larger quantity of logos. 11:07 during the spin, logos are starting to disappear for a second or so and then reappear and the spin has begun to get disjointed. It’s like the visualization of the spin is starting to lag. Seems to happen less severely or even occasionally not at all on short-duration/slower spins. I noticed throughout the test that the audio of the video that was just playing stays playing during the spin to the next title. Is that by design? I think the previous video remains up and playing in the background during the spin. 11:13 slowly getting worse. It’s not just the wheel that lags, but the text titles changing lag at the same points as the wheel. Despite the now-obvious lag while spinning, the video playbacks themselves remain smooth and lag-free. 11:16 the previously selected game is starting to flash back up on the screen for a second or two intermittently while the wheel is spinning to the next game. 11:17 Sometimes it takes so long for the lag to catch up that the spin kicks off again before it settles on a game. This may be the death spiral that ultimately crashes the app. 11:20 LB’s clock is no longer staying current with the actual time. Stuck at 11:17. The wheel while spinning is almost not visible at all. When it does stop on a game, the wheel visually displays in chunks before getting spun again a second later. 11:21 There’s almost no graphical content left on the screen the majority of the time. The lag is cumulatively so bad now that it’s just the theme background and the text elements that stay on screen. The images and video content flash on and off, and mostly stay off. 11:27 Interrupted Attract Mode to check Event viewer. LB:BB’s clock has refreshed to current time. While Attact Mode was not active, LB:BB Process was consuming 18% of CPU, 582MB of memory. Disk and network are both at 0%. Nothing else running on the machine comes anywhere close. When Attract Mode began again, it’s performance was still badly degraded. It did not clear up as a result of being interrupted. Maybe none of the video players are actually being unloaded all the way, and they gradually build up until the system runs out of resources? 11:36 LB:BB has stalled and is entirely unresponsive. Awaiting CTD. 12:23 Still hung and not responding. Hasn't CTD'd yet. Probably would have if I hadn't interrupted it to check the resource consumption.

That was definitely an intentional decision. The last thing I wanted to worry about on this build was hardware horsepower. I'm sure it would struggle to play the topmost tier of games, but those aren't in scope for this build anyway. I was pleasantly surprised it played Tekken 7 and KI flawlessly. Nah, the problems I've run into have all been, predictably, software quality-related (low quality rom dumps, pain-in-the-ass emulator configs, controller configs, etc). So chasing this Attract Mode annoyance is minor in comparison. Still, if there's a memory leak at play here (which is my current belief), if I can help the dev find and fix it, great.

Using those m.2 ssds via the Internal m.2 slots. Yep, and it is. This is a multicade build with some Windows/Steam games, console emulators, classic mame, v pinball (fx3, etc), and sinden lightguns (whenever they arrive), and front ports for USB controllers. I can play Tekken 7 via Steam, the Killer Instinct steam version, etc all just fine thanks to the integrated Radeon RX Vega M GL GPU.

Alright. I unplugged everything but the USB keyboard and the wireless mouse dongle (which have always been plugged in from the start), then powered it back up. I haven't touched it, and will watch Attract Mode to see how it goes. If it still misbehaves, I'll reboot, then also shutdown any/all background apps (though there aren't many... just GPU control center, etc). The first few scrolls kicked off as I was typing this, and they have been smooth (not jittery). Let's see if it gets worse the longer it stays in Attract Mode. I'll also time the durations.

No problem. I'm pretty patient, especially since I'm relatively new to the world of arcade building and frontends (though not at all new to the technology involved). Will I need to worry about Windows re-addressing my controllers when I plug them back in again later?

Not recently, no. That's an auto-populated Favorites playlist. Theme: AllNightLong (not customized). I'm still building my cab, so the machine is only powered up when I'm working on configuration or playing games. It's fully shutdown the rest of the time (not asleep).

See also: IMG_8541.MOV

I'm a recently new LB user, so I was running the stable version immediately preceding 11.9. I never let Attract Mode run for a prolonged period of time in the previous version, so I'm afraid I don't know if the problem existed then. What I can say is that the wheel spins erratically now, where before it used to spin smoothly. Here's my hardware: https://ark.intel.com/content/www/us/en/ark/products/126141/intel-nuc-kit-nuc8i7hnk.html Ram: 32GB DDR4 HDD: 2x 500GB Samsung 970 m.2 SSDs

Adding my event log for analysis. Purpose-built for a cab, Win10 x64. No other apps or usage. Just LaunchBox+BigBox, MAME and Retroarch. I haven't installed any other video players, etc. Video drivers were already up to date from the manufacturer. Crashes to desktop within an hour or so. Log Name: Application Source: Application Error Date: 1/30/2021 9:33:57 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: ARCADE Description: Faulting application name: BigBox.exe, version: 11.9.0.0, time stamp: 0x5fb3100b Faulting module name: coreclr.dll, version: 4.700.20.26901, time stamp: 0x5ec48a29 Exception code: 0xc00000fd Fault offset: 0x000000000004a4c7 Faulting process id: 0x237c Faulting application start time: 0x01d6f7864632d69d Faulting application path: C:\Users\LAUNCHBOX\LaunchBox\Core\BigBox.exe Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.6\coreclr.dll Report Id: 5f663230-da5f-4cd8-871d-d3e20a2d77b9 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2021-01-31T05:33:57.1474479Z" /> <EventRecordID>3505</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>ARCADE</Computer> <Security /> </System> <EventData> <Data>BigBox.exe</Data> <Data>11.9.0.0</Data> <Data>5fb3100b</Data> <Data>coreclr.dll</Data> <Data>4.700.20.26901</Data> <Data>5ec48a29</Data> <Data>c00000fd</Data> <Data>000000000004a4c7</Data> <Data>237c</Data> <Data>01d6f7864632d69d</Data> <Data>C:\Users\LAUNCHBOX\LaunchBox\Core\BigBox.exe</Data> <Data>C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.6\coreclr.dll</Data> <Data>5f663230-da5f-4cd8-871d-d3e20a2d77b9</Data> <Data> </Data> <Data> </Data> </EventData> </Event>

Just found this thread, hopefully a few months does not a necro thread make? I'm running 11.8 (stable) and am experiencing these same symptoms. I foolishly left "rough duplicates" checked, and it took my machine 36+ hours to complete a full rom import. It made it to one of the very last roms (zw-something) before hanging for 8+ hours on doing the rough duplicates check on that rom. I finally gave up in the morning and hit cancel, only for it to sit hung for over an hour. I finally gave up and closed launchbox. When I went back in to see the roms that had been imported, nothing appeared. It was as if the previous import process never happened. Discouraging, to say the least. I restarted the import and unchecked rough duplicates this time. I had only two errors throughout the first attempt and neither were fatal to the process. I don't know how the import is structured under the hood, but maybe placing a maximum cap on the number of roms per process would help? Something like "oh I see you're trying to import 30,000 roms. I'm going to split this up into 30 1,000-rom subprocesses where it finishes the whole import process end to end for each subprocess before starting the next." This would chunk progress and make it less risky to attempt a full (all or nothing) import. Especially for users like me who are not at all proximal to the Netherlands where these imports commonly take a very (very) long time.