Jason Carr

Hey guys, typically any issues installing the .NET Framework 4.7 are due to missing Windows updates. So generally, if you make sure you're 100% up to do with Windows Updates, and then run the setup, you should be fine.

Awesome. Thanks Dave.

Is this new with the 7.12 release?

Great to hear.

Hi @ckp, I just replicated this test exactly and the third ROM file was not deleted; it behaved correctly. Perhaps there was an additional app that you didn't realize was there? I tried using your exact data for testing since I have it but I couldn't find duplicates with different regions easily so I created my own test. If you are able to replicate it again and want to send me your data for testing, I can dive into this further. I am aware of the bin/cue issue when deleting ROMs.

Seems to be my motto too these days... To be honest it sounds like there's something fishy going on on that machine. I guess we'll see if other folks run into the same issues. Just don't understand how all that can come up after I've been testing for weeks on so many different machines.

I reached out to him recently; I hope he's not permanently done but he is at least taking a break for a while.

Announcement video from ETA is coming...

I haven't seen any real leaks with VLC, but yes, it does use a large amount of RAM, so it makes sense that memory would be significantly reduced when switching to WMP.

@NJDave71 Gotcha with the specs. Also make sure your CoverFlow image quality setting is set to Medium or Low or Lowest, as I discovered recently that 8 gig systems have a lot of trouble with CoverFlow using the full size images (you'll also have to refresh your CoverFlow images if you change that setting).

@NJDave71 @alnyden I'm putting out the official release momentarily. Let me know if you guys are still seeing those issues once you download the official release. @NJDave71, I'm most concerned with the lockups. Were they temporary or complete freezes? Try disabling any plugins to make sure that they're not the cause. Also, what theme are you using?

@ckp Of course, try as I may, I cannot produce any memory issues with your data. I have images and videos for most of your platforms, though it's possible that something could be caused by your specific media. Or it's possible that your hardware was having trouble keeping up with the garbage collection for some reason. In the tests I ran I saw the memory go up to 1.7 gigs at one point, but shot back down to 900 megs shortly after and spent the majority of the time in that range. I'm gonna go ahead with the official release here for now; we can revisit if you're still seeing RAM usage continue to grow as time goes on. I did heavily reduce the memory reduction routine as to prevent the video issues and hiccups that were caused by it, so it's not going to be as aggressive as it was before either.

Gotcha. Yeah, that's definitely caused by the aggressive RAM cleanups then. I'm planning on backing them off for the official release here.

@NJDave71 @alnyden How much RAM do you guys have? Those issues may be being caused by the aggressive RAM cleanups I put into place.

Alright, I've been using memory profiling tools to make sure that all loose ends are tied up, but maybe it's configuration-specific. Can you PM your data folder @ckp? I'm probably gonna go ahead with the release tomorrow since I doubt this is widespread, but I'll do some quick testing first to see if I can reproduce it.

Interesting. I haven't been able to produce any leaks on 3 different machines running for literally 2 days straight now. So I'm puzzled there. What version of Windows are you running again?

RAM is freed up over time once images are no longer being used, so yes, but it varies quite a bit and depends on a bunch of things, so I can't say how much.

@ckp Also check your Cover Flow image quality setting, as that makes a huge difference in RAM usage. On your 8 GB system it shouldn't be any higher than Medium. Since you're so concerned with RAM usage, you may even want to go to Low or Lowest.

Thanks @eatkinola. I'm going to assume that it's not an issue with this release. @ckp Not since the official 7.11 release; nothing has been changed that should ever cause *more* RAM to be used. However, as I stated I above I did add a mechanism to aggressively decrease RAM usage on low-RAM systems. The 1.7-2.0 GB of RAM use is normal and expected on a 16 GB system, as it's not as aggressive (the aggressive RAM reduction can decrease performance).

The memory leaks have been solved @ckp. That was the whole point of the last week of development I put in...

This is not at all a good idea as it could result in corrupt data files to routinely kill Big Box.

High quality is probably only noticeable in full-screen CoverFlow, where the images are bigger. I'm seeing a huge difference in RAM usage though between the Medium and Lowest image quality settings. Something like 400 megs.

Gotcha, that makes sense. I'm glad to hear that RAM is so low when you turn that stuff off.

Nice. Are you using WMP? Or do you have any videos in there at all?

One thing I'm noticing with the RAM requirements is that the CoverFlow image quality makes a HUGE difference. I'm seeing Big Box easily stay under 1 gig of RAM always when the CoverFlow image quality is set to lowest. The most RAM-intensive part of Big Box is indeed the CoverFlow images, just because there are so many of them on the screen at once and they can be pretty big once loaded into RAM. I'm finding that the highest CoverFlow image quality setting can even be a tad bit too RAM-intensive on 8 GB systems while running CoverFlow. Edit: I think what I might do is force a lower CoverFlow image quality setting on systems with less RAM.