Quote - IIRC, the memory leak problem is caused by the undo stack.

Adamr has released a script to clear the undo stack, and recover the memory.

 

Details are here:

http://forum.daz3d.com/viewtopic.php?t=143150

 

(I hope it is ok to post this here, I am just trying to help.)

...a very helpful script, already have it, and use it religiously. However, it only fixes the one related to shaders and content which are deleted from the scene (similar to the Carrara Delete Unused Shaders/Objects command).

There is still "memory creep" that slowly bloats the application while it is opened, and the application still sometimes hangs in memory after being closed down.  Had that happen the other night and only discovered it when I went to shut the system down and the "application open" warning appeared.  Going into the Task Manager/Processes, I noticed the DAZ process had stalled at 75MB even though it was nearly ten minutes after I closed the application.

The application also remains in a bloated state after a render completes or is aborted so any subsequent render process has less RAM to work with.

---

...forsaken daughter is watching you.

[Intel Xeon 5660 Hyperthreading 6 core CPU, 24GB GSkill Ripjaws 1333 DDR3 Tri Channel RAM, Nvidia Titan-X GPU with 12GB GDDR5 & 3072 cores, 1 x AData 240 GB SSD (boot) + 1 x 2TB HDD, EGVA 850 G5 PSU Antec P-193 with more fans than Justin Bieber.]