DAZ Studio 4.15 holds on to RAM

ColemanRugh

Why does Daz Studio 4.15 hold on to RAM for 2-5 minutes after it's been shut down?

I have to use Task manager to 'end task'.

What's it doing and why?

Windows 10, Ryzen 5 3600 cpu

Richard Haseltine

It's tidying up - if you force quit you risk corrupting various files.

margrave

Richard Haseltine said:

It's tidying up - if you force quit you risk corrupting various files.

Scene Optimizer recommends the user quit and restart, and I always have to kill Daz from the Task Manager since it won't open a new instance while the old one is running. Can you give more information on the side effects?

PerttiA

I don't remember... Were the issues with the second viewport fixed for real in 4.15?

Richard Haseltine

margrave said:

Richard Haseltine said:

It's tidying up - if you force quit you risk corrupting various files.

Scene Optimizer recommends the user quit and restart, and I always have to kill Daz from the Task Manager since it won't open a new instance while the old one is running. Can you give more information on the side effects?

It is possible to start a new isntance while the previous one is still closing, but it requires forward planning (either to launch a new isntance from within Daz Studio before closing or to create a short cut for launching) Daz Studio Pro 4.12 - instances

Richard Haseltine

PerttiA said:

I don't remember... Were the issues with the second viewport fixed for real in 4.15?

You mean the hang if the IPR toolbar was set to on but the AuxViewport was not open at any point during the sesssion? Yes, that was fixed (and coulrd be fixed before that by turning the IPR toolbar off in the Aux Viewport).

ColemanRugh

Thanks Richard!

bbaluchon

I noticed that as well, and while it's a bit annoying when you only want to restart quickly for various reasons (crash, updating morph content, etc.), better let the thing unload properly from RAM unless you want to risk corrupting files in some way...

Richard Haseltine

If it literally crashed it won't be shutting down.

margrave

Richard Haseltine said:

margrave said:

Richard Haseltine said:

It's tidying up - if you force quit you risk corrupting various files.

Scene Optimizer recommends the user quit and restart, and I always have to kill Daz from the Task Manager since it won't open a new instance while the old one is running. Can you give more information on the side effects?

It is possible to start a new isntance while the previous one is still closing, but it requires forward planning (either to launch a new isntance from within Daz Studio before closing or to create a short cut for launching) Daz Studio Pro 4.12 - instances

Will launching a new instance interfere with...whatever Scene Optimizer tells you to shut Daz down for? And is it related to this bit farther down that page you linked:

-cleanOnExit

• If specified, this option is used to determine whether or not application settings/data are removed when the application exits
• A falsey value does not override the standard behavior of purging the application's temp directory on exit
• Valid falsey values are 0, off, n, no, f, or false
• Valid truthy valus are 1, on, y, yes, t, or true

If I launch a new instance and it just hands off some cached full-sized textures rather than the optimized textures, that won't really help much.

Richard Haseltine

A separate instance is separate - it creates its own folder in AppData, possibly filling it with copies of the UI files from a different instance/release channel if you choose that option, and possibly clearing things out on launch and/or exit if you choose those options. I'm not sure what you mean by cached textures, but if you are thinking of things written to the Temp folder they are not shared.