Is there a memory leak in the update of Daz 4.24?

stripe6499_9253833ae8

I've just moved into my new home and finally have a chance to get back to work on Daz again. However, I seem to have a memory leak issue. It's always been the case that after working on Daz for any length of time, render times would start to stretch and require either a restart of Daz or the pc. Now, it doesn't seem to take many renders at all for this to happen. Render times suddenly seem to jump from 5-10 mins to 20-50 mins on the same scene (different camera angles and poses, but no added or changed assets). Is anyone else experiencing this issue or is it just me? 

Padone

The performance drop is probably due to iray switching to cpu mode. You can monitor the card usage on the task manager.

This is not necessarily a memory leak. In general a new version of iray or the nvidia drivers may use more memory than the previous one, usually to increase the speed or add new features. This unfortunately also means that a scene which rendered fine with a old version may not render in a new version because there isn't enough memory. If you are stuck with an old card and can't update the hardware, then you may consider to don't update daz studio either, or other 3d applications as well.

WendyLuvsCatz

the trick I use shared by another here is

switch the tab to hardware 

uncheck then recheck GPU to clear the memory

stripe6499_9253833ae8

TY, Wendy. I'll try that.

stripe6499_9253833ae8

Well, no luck with that on the first try. I'll have to dig into the logs.

stripe6499_9253833ae8

Padone said:

The performance drop is probably due to iray switching to cpu mode. You can monitor the card usage on the task manager.

This is not necessarily a memory leak. In general a new version of iray or the nvidia drivers may use more memory than the previous one, usually to increase the speed or add new features. This unfortunately also means that a scene which rendered fine with a old version may not render in a new version because there isn't enough memory. If you are stuck with an old card and can't update the hardware, then you may consider to don't update daz studio either, or other 3d applications as well.

Yep, i get that, but in this case, we're not talking driver updates, the render times are degrading with use from hour to hour, not after a driver update. Same scene, just different camera angles and poses. No lighting change.

 

thatbumzzz_788e56ddf1

I've been experiencing the same, even with the same scene where I just tweak it a little, come back later after lunch or dinner and suddenly a 5 min render is 10 min and noisy. Then I restart and its back to 5 min.

Padone

When iray falls back to cpu the denoiser can't work as it only works with the gpu, that's why it gets noisy. Again, you can check the task manager and the log and see what happens, but pretty often it's a cpu fallback. The typical error is "CUDA device ran out of memory and is temporarily unavailable for rendering". When you change the camera angle and poses, iray has to recompute the scene regardless, of course, as visible geometry and light contribution change. This means to discard old data and allocate new data, which may require more or less memory than the previous camera angle, depending on the shot, typically a long shot with lots of items will require more memory than a closeup with a few items, in the same scene.

You can also try to save some memory in the iray options. But again, a new version of iray or the driver may require more memory to render the same scene.

render settings > editor > optimization: 

• instancing optimization = memory
• ray tracing low memory = on

p.s. For dforce hair, using curves will require much less memory. You need to set the viewport tessellation to one and the render tessellation to zero for that.

p.s. You can also disable the cpu fallback in the iray options: render settings > hardware > scheduling. This way instead of falling back to cpu you get a black screen when there's not enough memory, so you can better understand what happens.

stripe6499_9253833ae8

WendyLuvsCatz said:

the trick I use shared by another here is

switch the tab to hardware 

uncheck then recheck GPU to clear the memory

Ahah! There are two boxes to uncheck, plus using Padone's tips for optimization settings seems to help. TY both.

WendyLuvsCatz

stripe6499_9253833ae8 said:

WendyLuvsCatz said:

the trick I use shared by another here is

switch the tab to hardware 

uncheck then recheck GPU to clear the memory

Ahah! There are two boxes to uncheck, plus using Padone's tips for optimization settings seems to help. TY both.

you shouldn't have the CPU checked in the first place

that ensures it keeps rendering on the CPU once over the limit, never to return to GPU 

(unless of course you want that)

unchecked it stops abruptly if too much, leaving you a black image and choices to make to optimise it more instead of waiting in misery as it painfully, slowly struggles on the CPU

stripe6499_9253833ae8

~nod~ I understand, but there are two separate GPU boxes in the hardware tab. That's what I was refering to, not the CPU box.

thatbumzzz_788e56ddf1

Should CPU fallback be checked off too?

WendyLuvsCatz

thatbumzzz_788e56ddf1 said:

Should CPU fallback be checked off too?

only if you don't want it using your CPU when it exceeds your VRAM which in my case at least will freeze up my whole computer

if you own something like a Threadripper, you might want it checked for scenes you know won't fit on your card