Jump to content
LaunchBox Community Forums

Xpendable

Members
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

1 Neutral

1 Follower

About Xpendable

  • Rank
    8-Bit Processor

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Xpendable

    BigBox memory issue on computers with 4GB ram

    Actually I misspoke. It's actually a 970GTX. Even if it was a 770GTX, that is way overkill for the front end and mame. I know this because I previously used a 10+ year piece of crap $49 gt card and this all worked fine. Absolutely no difference. You aren't leveraging much of the graphics card to be honest. No shaders or meshes, right? I used to code for both openGL and DirectX, so I actually have some experience here. Yep, get this is a lower priority.
  2. Xpendable

    BigBox memory issue on computers with 4GB ram

    I will try setting up a scheduled task to reboot the computer nightly. That should more or less resolve my issue since it appears to take at least a day for things to go south. Worst case scenario I could do it twice a day.
  3. Xpendable

    BigBox memory issue on computers with 4GB ram

    1. Ok, memory issue occurred using the default theme & vertical wheel 2 as well. On startup, BigBox is using around 800-900 mb. After < 24 hours, it's using > 2 GB of RAM. Shutting down BigBox and all the memory comes back. 2. I did just renew my license for another year (had expired a couple of days ago) and updated to 9.4 Beta 10. 3. I confirmed that I was indeed using Windows Media Player for video playback. I switched back to VLC and noticed video corruption right away in many of the game videos. I believe this is why I switched to WMP in the first place. I just did some searching, and I see a recommendation to install the K-Lite codecs which supposedly resolves the issue. I just downloaded and installed that and I'm trying it now... Nope, this does not seem to resolve the issue. The animations (on top of the video) are also sluggish with VLC. By the way, I have a pretty beefy graphics card in this system... Nvidia 770GTX. Did some more testing and BigBox in general has gotten sluggish as hell with VLC. I can hear the hard drive thrashing like mad, which doesn't happen when I use WMP. When I switch to WMP, those problems go away entirely. Why is VLC the recommended video engine? A quick search and it looks like I'm not the only one who has problems with VLC. Here's a YouTube video I made showing the difference in performance between VLC and WMP on my computer:
  4. Xpendable

    BigBox memory issue on computers with 4GB ram

    My fault, I misunderstood what CoverFlow meant. I thought that was a theme name, but that's not correct, right? Does CoverFlow refer to certain view types? The theme I am using was "Unified" and the view I was using has a vertical wheel on the right. So I guess I am not using CoverFlow at all, I'm using a clear logo wheel. Again, my bad. If memory serves, I am using Windows Media Player for the video playback. When I first installed LaunchBox, I recall that I couldn't get the VLC to work... I'll take a look at that again and confirm.
  5. Xpendable

    BigBox memory issue on computers with 4GB ram

    So after running for more than a day, BigBox RAM usage increased to 2.62GB (from 2GB). That sort of proves there is a memory leak before it taps out at the max .Net allows. At this point Windows reported that it was low on memory and recommended that BigBox.exe be stopped. I caught it before memory was exhausted so no crash occurred. Also I was using the Unified theme, if that helps. I'm trying a new test with the Default theme to see if I have the same problem. Also, I have always used the game clear logos. And a reminder that this problem never occurred until after an update within the last few months.
  6. Xpendable

    BigBox memory issue on computers with 4GB ram

    Shoot, I already have CoverFlow Image Quality set to Lowest (Fastest). One more thing... after a fresh reboot and after BigBox is started, total memory usage for Windows 7 + BigBox is about 2GB. Meaning, there's about 2GB free. It will be interesting to see what that looks like after 4 hours, 8 hours, 12 hours, etc.
  7. Xpendable

    BigBox memory issue on computers with 4GB ram

    Thanks, I'll give that a try.
  8. Xpendable

    BigBox memory issue on computers with 4GB ram

    Some more information for you, Jason. I am indeed using CoverFlow. The crash occurs after running for several days. I have Attract Mode set to NOT cycle platforms. It always stays on my "Arcade" platform (MAME) which has about 1536 titles. I've captured the .NET crash below... it is the exact same error on every crash: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-02-04T13:24:37.000000000Z" /> <EventRecordID>21005</EventRecordID> <Channel>Application</Channel> <Computer>HTPC</Computer> <Security /> </System> - <EventData> <Data>Application: BigBox.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ComponentModel.Win32Exception at MS.Win32.UnsafeNativeMethods.RegisterClassEx(WNDCLASSEX_D) at MS.Win32.HwndWrapper..ctor(Int32, Int32, Int32, Int32, Int32, Int32, Int32, System.String, IntPtr, MS.Win32.HwndWrapperHook[]) at System.Windows.Threading.Dispatcher..ctor() at System.Windows.Threading.Dispatcher.get_CurrentDispatcher() at System.Windows.Media.Imaging.BitmapDecoder..ctor(System.Uri, System.Windows.Media.Imaging.BitmapCreateOptions, System.Windows.Media.Imaging.BitmapCacheOption, System.Guid) at System.Windows.Media.Imaging.PngBitmapDecoder..ctor(System.Uri, System.Windows.Media.Imaging.BitmapCreateOptions, System.Windows.Media.Imaging.BitmapCacheOption) at DynamicClass.(System.Object) at Unbroken.LaunchBox.Wpf.Controls.CoverFlow.ThumbnailManager.Worker(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch()</Data> </EventData> </Event> It appears to be loading content when the crash occurs. When the crash occurs, Windows is so exhausted of memory that it cannot even display Task Manager! In true .NET fashion, as soon as I kill BigBox.exe, Windows recovers and the memory that the .NET program had been using is returned. I believe that 4GB is simply NOT enough memory, at least for the number of ROMS I have in my arcade wheel. Probably as it's approaching all remaining free memory, the crash occurs because the OS does not have enough resources. You probably never see this because I'm betting a computer that has more than 4GB of ram will be capped at 4GB (possibly default limit on a .NET program... and since there is still plenty of ram left over for the OS, everything is fine.) I'm assuming you are compiling 64-bit and not 32-bit, but that would still be irrelevant in my case with only 4GB of RAM (and less than that would be available for BigBox). One final thought... this problem NEVER occurred for most of last year, I have not added any roms or changed any media. No other changes have occurred on this computer. That would mean a program change is causing a problem where one didn't manifest itself before. Food for thought.
  9. Xpendable

    BigBox AttackMode with LEDBlinky not working

    Surprised that no-one else has this problem. I've contacted Arzoo and he's giving me some debugging tips which I haven't had a chance to do, but will soon.
  10. Xpendable

    BigBox memory issue on computers with 4GB ram

    I did disable the startup screens and the problem went away. I also think there is a memory leak. BigBox is crashing after a day (even if nobody plays anything on my machine) due to being out of memory. My computer unfortunately only has 4 GB of ram which I'm unable to expand due to something being wrong with the 2nd memory slot, so at the moment, adding memory isn't a solution for me. Others probably have more ram and aren't as likely to see this as often if at all.
  11. Xpendable

    BigBox memory issue on computers with 4GB ram

    I don't believe I am using retroarch for mame but I will try disabling screens to see if it fixes the problem.
  12. I'm having major problems. After a recent update, BigBox is hanging on the second game launched. It doesn't matter what game you try to launch (only talking Mame at the moment), it launches the WRONG game and it get stuck and I can't get out of it. I have to forcefully kill BigBox via TaskManger and restart it after EVERY game. What is going on here?
  13. I don't know if I have something configured wrong or what, but as soon as Attact Mode starts in BigBox, all LEDBlinky animation stops. As soon as I touch the controls, the LEDBlinky FE Active animation resumes playing. How can I get animation to play while AttactMode is running?
  14. Xpendable

    Games Disappearing from my launchbox libraries

    I am having this problem, too. Many of my games have disappeared for unexplained reasons. What gives? :(
  15. Thanks for the tip. However, I was able to solve my issue by tweaking frameskip while in a MAME game. I think it is F8 and F9 that decrease and increase frameskip.
×