FIXED with latest version (6.2.85): Memory fills up when rendering via the queue

Started by sethcshort, May 11, 2016, 12:47:46 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

sethcshort

I first noticed this bug when my computer started getting very very slow and renders were taking a long time.

I opened Task Manager and found that my RAM (16GB) was completely full. Keyshot was taking up 14.5GB of that.

I created a new scene in Keyshot, so there was nothing in the scene, but the memory usage didn't go down. The only way to clear that RAM was to shut down Keyshot and restart it. Upon restart it was back to < .5GB.

Per this post -- https://www.keyshot.com/forum/index.php?topic=11313.0 -- I did some tests and I think it could be the render queue not releasing memory after renders, I'm having a very similar experience to that person.

I've attached a screenshot of my Task Manager during the test. As you can see, when I'm adding stuff to the queue, and then when the queue is rendering, it uses more and more memory and never releases it.

I tested it when I'm manually rendering one image at a time (not adding it to the queue) and the memory usage doesn't change AT ALL. It's a completely flat line.

My specs:

Windows 7
Keyshot 6.1.72
No plugins
The models came from Inventor. The total file has around 8 million triangles, there are 40 nearly-identical objects, so each render is around 200,000 triangles.
Due to NDA I'm not able to attach the Keyshot file.

guest84672

Yes - this is fixed in KeyShot 6.2. I can send you the BETA version if  you want. It is very stable.

theAVator

I've noticed issues like this ever since upgrading to KS6 (never had any troubles in KS5). I've had the same thing happen with 32GB RAM, even to the point where the programs crashes because of it. Some of the KS guys made some suggestions to try for mitigating the issue.
What I've seen to have helped is:
- switch from advanced rendering options to Max Time (calculated using the Max Samples). This doesn't seem to use as much memory as the advanced option.
- Once you have the queue built, close KeyShot and make sure the working memory spins down to zero and the process quits
- Quit other programs that might be using memory (for me Adobe creative cloud, snagit, onenote, chrome, etc)
- when you open KeyShot, don't load the model - just use the default blank scene. Open your render queue and hit the process queue button.

This just helps starting with the lowest amount of used memory and then not using as much in the process as well.

Good to hear of a fix in the next update!

guest84672

Again, if you want to get access to the 6.2 BETA build, please e-mail beta@luxion.com

Note: this doesn't apply to hackers and crackers.

sethcshort

As this is my work computer, I didn't feel comfortable installing beta software. But Keyshot 6.2. I just updated to the latest stable version (6.2.85) and the render queue memory issue is gone. See new screenshot attached... the memory is released after each render. Thanks guys!