Out of memory error after computer wakes up

[underdog32]

I have big box on a cabinet.  My cabinet has a power button that hibernates the computer.  Every time i hibernate it and wake it up again bigbox freezes.  When i close the window from the task bar a hidden out of memory error shows up.

I have 64gb of memory, and <20% of it is used at the time the error appears.  None of my drives are low on space so i don't think it's a page/swap file either.

Any ideas on what i can do to fix this?  I have young kids and i want them to be able to just press the button and wake the machine to play.  In addition it takes a while for big box to load so restarting it each time the computer wakes up isn't desirable.

[clkish1988]

Did you ever get anywhere with this?

[underdog32]

4 hours ago, clkish1988 said:

Did you ever get anywhere with this?

Sadly no.  I've resorted to shutting down big box before putting the computer to sleep.  Something isn't waking up fast enough for big box to access it or something.  It would be nice if big box could put a retry before throwing that message maybe.  

[cyborc]

I've had the same issue. Like @underdog32, I also have high amount of RAM. (128GB). I can't find the post at the moment but someone on reddit suggested manually setting the paging file size. By default it's set to be managed automatically by Windows. At first I set it to 4096MB as the initial size and 8192MB as maximum size, but the crash on wake still occured. I changed it to initial 8192MB and max 32768MB and I've now done several sleep/wake cycles without launchbox crashing. Seems a little silly to crank the paging file up this high but it seems to work so far.

Edited March 19 by cyborc

[AstroBob]

Hi Folks,

Thanks for the reports here. Just to let you know we think we've identified the cause of this and hope to have something out in our next beta. I'll post here again once that is available. 

Thanks for bearing with us and sorry for the issues caused here. 

Cheers,

[AstroBob]

Hi there, 

Just to let you know this has been addressed in 13.21 beta-1. You can find details on this here, or wait until the 13.21 official release to receive this fix. 

Thanks for bearing with us while we got this sorted