Jump to content
LaunchBox Community Forums
We1Dont7Die

Launchbox ignoring RAM limit

Recommended Posts

I've noticed that launchbox ignores the RAM Cache limit setting. If I set it to 2048 MB it ignores it and climbs to around 5GB. If i set it to use 4GB ram, it still ignores the limit and ends up at about 5GB usage.

 

I'm using 8.2 beta 6, but this problem was happening in the stable release as well, I just hadn't had time to report it.

Share this post


Link to post
Share on other sites

Now just to be sure you are talking about 100% LB right because that limit set in LB has no effect on BigBox

Share this post


Link to post
Share on other sites

yes I'm aware of the setting just wanted to make sure you weren't setting it in LB and then not seeing it work in BB as unlike other LB settings it doesn't effect BB that is all but since you only using LB then I have no clue I've used that setting to turn it all the way down on lower end hardware with only 1 or 2 GB of RAM available and it makes the application usable and out of memory errors will stop happening so I know in those scenarios it usually works. Do you have videos in LB and are you using VLC for the playback or WMP I know people have linked VLC to memory leaks in the past but I don't recall if it was with LB or BB specific but might be worth a try to switch.

Share this post


Link to post
Share on other sites

Also to add to this, the ram cache setting in Launchbox is for caching images into ram in order to speed up the fetching of said images, the program of course will still have to run as well so that will of course use more ram over the top of what you have set for the image cache. 

Share this post


Link to post
Share on other sites

5gb seems high though I just opened LB to test and its using 137 MB initially and as I scrolled through 5 or 6 systems (some rather large like NES and GBA) it gets to right about under a gig and won't go any higher I have mine set for 1024MB in LB

Share this post


Link to post
Share on other sites
11 minutes ago, DOS76 said:

5gb seems high though I just opened LB to test and its using 137 MB initially and as I scrolled through 5 or 6 systems (some rather large like NES and GBA) it gets to right about under a gig and won't go any higher I have mine set for 1024MB in LB

I just scrolled every platform in my library and it seems about right to me, I have the cache set to 4GB.

 

Screenshot (436).png

Share this post


Link to post
Share on other sites
On 3/31/2018 at 6:53 AM, DOS76 said:

yes I'm aware of the setting just wanted to make sure you weren't setting it in LB and then not seeing it work in BB as unlike other LB settings it doesn't effect BB that is all but since you only using LB then I have no clue I've used that setting to turn it all the way down on lower end hardware with only 1 or 2 GB of RAM available and it makes the application usable and out of memory errors will stop happening so I know in those scenarios it usually works. Do you have videos in LB and are you using VLC for the playback or WMP I know people have linked VLC to memory leaks in the past but I don't recall if it was with LB or BB specific but might be worth a try to switch.

I m using VLC, yes. Ill try switching to WMP.

Share this post


Link to post
Share on other sites

Just out of curiosity, when the RAM limit does work, does it simply stop more cover art from loading? or does it flush cover art from ram as you scroll?

Share this post


Link to post
Share on other sites

I'm guessing it flushes it as the further down the list I go I get box art still. I have a tablet with 1GB or RAM if I add more than like 600 games without it turned all the way down I will instantly start receiving out of memory errors so in that case I know its working.

Share this post


Link to post
Share on other sites

The RAM cache code has not been touched in literally a year, and I haven't heard about any issues for a very long time, so I'm pretty doubtful that it has a leak at this point. That said, the RAM cache has nothing to do with the total RAM usage, so you can't really assume that it has a leak based on total RAM usage (there's a lot more in LaunchBox that uses RAM than the RAM cache). It's also worth noting that the "RAM cache" as it's known in LaunchBox currently will be removed entirely once LaunchBox.Next is completed and we finish that migration. WPF has its own improved methods for managing images cached in RAM.

To answer your last question though @We1Dont7Die, it flushes out the last used cover art to make room for new art when the RAM cache fills up.

  • Like 1

Share this post


Link to post
Share on other sites

Updated to beta 7 and selected WMP as video player. It's still using over 5GB ram when set to 2048MB. No big deal for me as I have plenty of ram, but I could see how this may be an issue for someone else down the line.

Share this post


Link to post
Share on other sites

I would be curious as to how many game entries you have in LaunchBox? Others may be able to chime in, and if than for no other reason, confirm the amount of ram used on their system for a like number of entries, or not.

I, for one, only have about 4100 entries and don't see the ram usage you are reporting.

Share this post


Link to post
Share on other sites

I am re configuring LaunchBox from scratch and will stick to the stable releases for the time being, but once im finished getting it set up again i will revisit this issue to see if it persists. Probably a day or two.

Share this post


Link to post
Share on other sites

yeah it's pretty simple to reproduce this. i can see that as well.

i just set 2GB for the cache. 

then i went to the All platform and just started scrolling. I'm well over 2Gb and climbing as I scroll.

i assume the cache should be limited to 2GB and then LB itself gets to have some memory too.

so, i kept scrolling in All and got past 3GB but only half way through scrolling.

i have 12k games

Share this post


Link to post
Share on other sites

image.thumb.png.86e3a65224db6beedee0d1440287cce9.pngi would say there is a problem here  =) 

  • Like 1

Share this post


Link to post
Share on other sites

my normal setting for ram cache is 1024 (1GB) and I do not see this problem with 1024 set. so, you might try using 1024 @We1Dont7Die

Share this post


Link to post
Share on other sites

I haven't seen that behavior guys but rest assured that it will be fixed with LaunchBox.Next, which should be feature complete very soon. So at this point I'm just gonna say let's hold out until .Next is complete.

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×