Loading...
> >

DAZ not freeing up VRAM

michaelmszabomichaelmszabo Posts: 1
edited May 2021 in Daz Studio Discussion

Hi there,

I've had really annoying problems for weeks now. The root of the issue is that DAZ often does not free up VRAM after a render is finished, thus requiring a restart of DAZ almost every time I did a render or dared to use the Iray preview. I have to not only exit DAZ but kill an orphaned process via task manager after DAZ has closed. Any solutions? DAZ Log does not show errors (only those when it has run out of RAM)

 

My setup:
RTX 3070

Ryzen 7 3700

32GB RAM

Post edited by michaelmszabo on

Comments

  • meganappstatemeganappstate Posts: 85

    That's been the case since iRay was first introduced. The fact that it's not been fixed at this point indicates that DAZ consideres it expected behavior, so dn't hold your breath watiing for it to be addressed.

  • Richard HaseltineRichard Haseltine Posts: 102,857

    I think the issue is Iray rather than DS, but it has always been the case. What is process you are hasving to kill, that shouldn't be necessary (if you mean the Daz Studio process it is probably running clean up, so don't kill it unless it shows 0% activity).

  • michaelmszabomichaelmszabo Posts: 1

    Hi, thanks for your answer :)

    It's either a Daz Studio Process that never finishes instead goes on about 10% CPU usage forever or a process with the DAZ icon but no name.

  • PerttiAPerttiA Posts: 10,024

    Not freeing up VRAM between renders doesn't appear to be a problem, it feels like it keeps some data in VRAM in case the same scene is rendered again, but it is important to save/close the rendering window once the render is finished as that does reserve VRAM that's not available to any subsequent renders unless the window is closed.

    I have had DS hanging twice when closing. Both times I had left the content library open in some sub-folder, usually I choose the root folder before closing DS and no hanging.

  • Richard HaseltineRichard Haseltine Posts: 102,857

    michaelmszabo said:

    Hi, thanks for your answer :)

    It's either a Daz Studio Process that never finishes instead goes on about 10% CPU usage forever or a process with the DAZ icon but no name.

    It probably will close, it sounds as if it has a lot of clearing up to do - often the case with morph-heavy figures. It's single-threaded so you see only one core's worth of activity. Force-closing can damage the settings files or even the database, so it is to be avoided; you could start a fresh instance instead Daz Studio Pro 4.12 - instances

Sign In or Register to comment.