That is basically the understatement of the year, lol
It seems that it doesn't matter how much memory your PC has... DAZ will look for and claw every damn scrap of it. I really wonder how these people managed to run and use two instances of DAZ running at once (I guess some earlier versions could do that) That must have been before the Iray days.
I think that is why a lot of full time game devs run two boxes, one for working on and one to just do renders. I think I'm going to set something like that up in the future, with a shared NAS drive between them so i can update the scenes and what not, even when the other box is rendering.
I'll give you some examples of how DAZ memory leaks affect my system, which is brand new (I only built it 1.5 months ago)
I have 32 GB btw, but my vid card is only a 4GB 1050Ti so everything falls on the CPU (8 threads)
- When just running DAZ and composing scenes, I can run several other apps and have multiple windows/monitors open, NP
- Soon as I start rendering, I have to limit myself to my browser, and maybe play a video or stream some music with a player.
- Anything that uses system ram is basically shut down... for example, try to download a file from MEGA when mid-render. MEGA saves the file directly to RAM until it's complete, then transfers it to your drives, so it slows to a snails pace when rendering.
- Torrents, on the other hand, work blissfully unaware of DAZ. I've done GB/s torrents while rendering.
- If you are rendering multiple small scenes and don't reload DAZ in between, it gets even worse as DAZ assets tend to stick around in memory. The 'clear the scene' button helps but all the advice I have read says it's best to close DAZ and then reopen it to clear the memory. Basically every batch render script will do this by default.
- Sometimes my file explorer will just go BOOM when the memory leakage gets too high. I'll go to move a render file and then my file explorer disappears and the desktop refreshes. My guess is the thumbnails Windows like making for everything bumps heads with DAZ.
- I like streaming my Prime movies when rendering so i have to start the service then wait for Prime to claw enough memory back from DAZ to start a good HD stream. It's OK after that, except for the odd glitch when DAZ does a particularly big write.
EDIT: I just re-read your post and are you saying DAZ acts like this, even after the render is finished? If so, then I wonder if you are loading scenes in that are too massive for your system?
Also, when you render, do you write to file direct or have the render in a new window? I use the later personally, as i like to see the progress being made. I also like the option of choosing whatever name i want for the render when it's done. Not sure if that makes a difference though.