Quote - ...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.

Which would account for Windows not realising that the GUI had vapourised working in Shader Mixer on my machine... as far as Windows was concerned, DS3Adv was still up and running. Usually you get a notice "this program has stopped working. Would you like Windows to diagose the problem" thingie. Never got that, so I could never send a report to MS about it. And Daz pretty much ignored my reports - just added them to the queue. Sort-of gave up after a while. :blink:

Monterey/Mint21.x/Win10 - Blender3.x - PP11.3(cm) - Musescore3.6.2

Wir sind gewohnt, daß die Menschen verhöhnen was sie nicht verstehen
[it is clear that humans have contempt for that which they do not understand] 

Metaphor of Chooks