Memory/resource leak causing out of memory errors, requiring reboot, daily

[Chris Edgar]

So I’ve been using beta 13 and 14 to do a lot of work in LB this past week, and it seems to be permanently scuttling resources – shutting everything down and re-running it does not clear up the errors. I have to reboot and it’ll last another day or so. Pretty sure it’s LB doing it, as I’ve been doing almost nothing else, and have been building up my DB and doing hundreds of edits over the past week. It’s not entirely impossible that it’s something else, but I can say I haven’t gotten out of memory errors before I started using LB heavily.

Apologies if this is a known issue.

[Christian]

Could you send a zip with your data folder in it to me via the forums (C-Beats). May help track down what is going on.

[Jason Carr]

Hi Chris, when you say that shutting LaunchBox down and re-running does not fix the errors, do you mean exiting and restarting LaunchBox?

Also, what are you system specs? How much RAM do you have? What version of Windows are you running?

[Chris Edgar]

So sorry for the delay. Yes, I’ll send my data files.

Yes, that’s correct, exiting and restarting. (I’m making sure in Process Explorer that it’s not persisting.)

Windows 10. 32GB RAM. 8th-gen core i7. GTX 1070 with up-to-date drivers. Windows up to date but not dumb enough to click on “check for updates”.

I was thinking about it, and the other thing I’m using heavily lately is GIMP for box images… so I guess GIMP could be the culprit as well. I’ve upped the desktop heap size and gotten another 32GB of RAM, so I’ll pipe up if I have the problem again.

[Jason Carr]

Okay, thanks. The thing is, LaunchBox and Big Box cannot hold onto RAM after they have exited, so I don’t see how they could be the issue.