Daz shutdown times
rwetmore
Posts: 20
Can someone please explain to me why Daz Studio (4.21) can require as much as 45 minutes to shut down after the app is closed? Watching Task Manager during the process shows a CPU load of around 3% and memory allocation that glacially decreases over time, often plateauing at certain memory amounts for minutes at a time. Watching disk activity shows that the delay isn't due to writing out caches or logs.
This happens on a fairly speedy system (well, it was a year ago when I built it): Ryzen 9 5950X, 128GB RAM, Windows 11. This happened before and after a complete system reinstallation, so I know it's not a particular interaction with a corrupted OS driver or with other apps. When I reboot my system while Daz Studio is running, it shuts down fairly quickly, meaning, I assume, that its processes are being killed rather than being allowed to shut down normally. It doesn't seem (?) to affect the app the next time I launch it.
I'm stymied, frankly. Can't CPU usage be increased during shutdown? Has there been any kind of audit to show what the app is doing during these 45 minute procedures?
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Have you tried using http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/plugins/plugins_load_config/start to ensure that only the Daz plug-ins load, the rstarting DS and testing that for shut-down speed? It can take a while to tidy up, but forty-five minutes does sound extreme.
Yes. It turns off all of my ManFriday plugins that I use all of the time, and does nothing for shutdown times. As I type this, I'm 16 minutes into a shutdown and there is still 11gb of memory (from an original 18gb) that Daz is screwing around with.
System logs don't show anything too out of the ordinary. Occasionally, when Daz has hung for awhile, the system posts an AppHangTransient event, but not every time.
Now at 20 minutes in, memory usage is down to a mere 9gb. Sigh.
I just Right click and End Task in task manager these days. Been doing that for several years now due this issue.
Use at your own risk as it can cause problems, including needing to reinstall the program.
Did it just start doing this? If so did you do any updates to the system lately? 45 Min is quite long and shouldn't be happening.
No, it's done it all along although it's less noticeable with my workflow (if Daz doesn't crash, which it constantly does). I can always count on at least 20 minutes for a shutdown—the reason I left the original post was it took 45 minutes for the last and I was, I hope understandably, a little upset. Yesterday's shutdown ended up taking 24 minutes, which is about average.
I do that occasionally when I have to get right back to work (I use Daz Studio about 14 hours a day for my job) but you're right--I've had to reinstall the app a couple of times which I assume is tied to this tactic. It would be a lot easier for me if I could understand the justification for any kind of shutdown that takes more than a few seconds. I mean, what the heck is the app doing during these extended epileptic seizures??
I'm pretty sure I've tried something like that in the past, but I'll try it tonight when I shutdown for the day. I'm sure you're right in that clearing scenes is a large portion of the shutdown time. I do deal with pretty massive models. My rendering system has two 3090's and I regularly reach their 24GB VRAM limit. I've always wondered why Daz takes so long to clear out existing scenes. I wish someone would explain why it takes so long for a processor that can execute 5 billion instructions per second to do that...
One thing that I have stumbled on, were duplicate morphs that were erroneusly included in some products, they clearly increased the time it took to shut down.
If one is familiar with the structure of the Data folder, it isn't that hard to find them. One could start searching for the morphs in the starter essentials.
Just make sure they are in fact duplicates as the filename can be the same even between different morphs.
Search the whole Data folder as G8 morphs can be included even with clothing items.
To avoid long shutdowns I save the scene I'm working on, then start a new blank scene, then shutdown DS. It closes in a few seconds, and is much simpler for me than deleting everything manually from the scene.
Ditto. "New" works really well for me, too.
-- Walt STerdan