NWjs stacks OS memory with the browser "reload" action.

Hi. So I've been playing around with using the browser reload action combined with manual loading of big assets from URL to improve memory management. I've had success with this in all browsers, even with NWjs preview. However the only instance it doesn't work is NWjs export. Here the OS memory stacks on each reload, making the 32-bit game crash after loading 10-20 times. This seems like fixable problem, but is it? Anyone have any experience with this?

Thanks

My best guess is that Chromium's mediocre memory management system (Garbage Collector) isn't doing the job when it's supposed to.

NW.js allows us to expose the garbage collector and trigger it on demand to instantly unload things from memory.

You can find steps to expose GC in my NW.js Roundup, feel free to test out How To: Force GC To Instantly Unload Audio From Memory and share your results in here.

(It's not just unloading audio by the way, it's unloading everything in the "waiting line" which is mostly just audio.)

TheRealDannyyy Thanks, I'll make sure to test it!