Daz Studio remains in memory
mumia76
Posts: 146
I recently started to have this issue that when I close the main window using the X, the window closes but the program keeps running in the background, using memory and cpu time, unless I kill the task using the task manager.
Anyone else noticed this?
It was happening with both the latest release version and the one before that .117 and .118 I think.
It doesn't always behaves like this, but very frequently, about 9 out of 10 times.
It seems to have started happening after I installed Daz Central. But that might be just a coincidence.
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
How long are you waiting, and is there activiity shown in Task Manager? DS does need to do some house-keeping as it closes, how much depends on the complexity of the scene (and undo stack) in memory when you close. Some third-party plug-ins are associated with a stalled exit (that is, without CPU/memory activity). It is not a good idea to close DS witth Task Manager.
I waited for about 2-3 minutes maybe longer for it to go away but it didn't. I didn't measure the time exactly. The memory usage is fluctuating and it seems to pin one CPU thread to 100% like it's in an infinite loop or something.
This happens with relatively simple scenes as well, like one figure and hair, nothing else, not even lights in the scene.
Previously when I closed it it always disappeared within seconds. I used to close then reopen Daz Studio when I wanted to open a new scene, because simply opening over an existing scene takes a thousand years. And it always worked up till about a week ago, when it started doing this. I can't open a new instance of it while the old one is in memory. So I'm definitely going to continue killing the task until there is a proper solution.
Maybe this is non-ralated but I notice often Daz prevents Windows from shutting down unless I exit Daz manually before issuing Windows shutdown command. In other instances like this it's usually with programs with known memory leak issues.
Edit: to mimia75 - Do you restart your computer often? If you don't and Daz3d does have a memory leak issue then that could explain your symptoms. Some memory leaks won't be resolved even with killing the process in Task Manager. In those caes you want to restart the computer even after killing the process.
OK, but why does this just started happening recently? What is there to clean up? Exiting should just mean releasing allocated memory end of story.
For me it has been present for a while - perhaps it's become more noticeablle as you've added content, or perhaps something like security software has been updated and now behavces in a way that slows the process.
I already had a huge library with endless strings of morphs from various sources. It takes about 3-4 minutes just to create a new G8F character that was normal for me for years. But this is completely new, it didn't gradually increase, what was literally less than 5 seconds is now 5 minutes. Perhaps the amount of installed assets just exceeded some theoretical limit. Or it could just be caused by one product, but since I have hundreds, I'm not going to start uninstalling one by one. So this will remain a mistery, unless it solves itself eventually. Wouldn't be a first.
I came here to post about this. When I shut Daz Studio down, it remains in memory. Not for just a few moments, but permanently, unless I use 'end task'. I seem to remember that this would happen occasionally before, but now it's every time I run it.
Have you tried disabling third-party plug-ins to see if that fixes the issue? This script http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/samples/plugins/plugins_load_config/start can be used to disable them on the enxt DS restart, you can then (if it does fix the issue) reenable them one-bu-obne in Help>About Installed Pllug-ins (followed by a restart) to identify the culprit if that is the issue.
How long do you consider being "Permanent" - I monitored the situation with CPU-Z and after about 20 minutes, DS released all the memory and VRAM it had reserved.
128 GByte RAM here, memory consumption of DAZ at 2.3 GByte (small scene). Hangs for hours/endlessly/until I kill it.
I have this problem since years (Beta latest), support couldn't help me out but promised me to "have an eye on it". I just don't understand why the application just can:
Does DAZ Studio use some sort of built-in garbage collection? What exactly is the reason it's not shutting down?
When I had octane plugin enabled, DS would stay till I killed it VIA task manager. Without it, most times it's done doing whatever it's doing in a few minutes.
wait, how old is daz? Does it still have a 640k kernal somewhere?
Daz is lousy at house-cleaning ... I can load one of my building bases into a scene in 20 secs... but trying to delete one, which only happens accidently now, can just leave daz sitting there with its "white screen" of non-responding
the one where you get the dialogue box "the program is not responding would you like to wait, etc".
---
I would love to see Daz rev up and use some cpu cycles.
Takes 3 minutes to load a g8 figure and yet cpu usage is minimal .. like everything is being filter through one 256 character buffer?
---
way back in the early days of mac when you told it to copy you could see it go copy write, copy write, but you could change the parameter so it would READ WRITE a much bigger chunk each time.
---
only time Daz uses the CPU is when you 3dl or an iray pops off the gpu and then you better have a limiter in place because it will take every last cycle available.
(It's rumored that there are programs in existance that actually self limit to prevent them from running away and locking up a machine.
---
But Daz doesn't seem to housekeep after closing a render... (although it does seem better on that now).
And it the amount of time to delete something is an indication, shutdown is slow.
---
why do I have multiple dazs running? so I when I save one, I can go do other work.
I have waited upwards of an hour for Studio to shut down cleanly, and that's with only Measure Metrics as a third-party plugin.
Studio seems to have trouble managing it's memory. I know because successfive renders of the same scene with minor changes take longer and longer. However if you save your scene, reopen it, it takes a lot less time. Something is wierd under the hood with how it handles memory, and how long it likes to be open before closing down and starting anew.
Same thing; if DAZ crashes out of a render (because I was an idiot and had half a dozen other things going on) and then I exit DAZ, I'm almost always unable to restart it immediately. Watching through Task Manager, I see Daz take anywhere from 15 seconds to a good 3-4 minutes to finally unload itself.
Still in memory... is still in memory, dont put OUR FAULTS like DEV to us, ty!
I'm not sure what you are tryinmg to say. By design DS clears itself from the task bar/dock and cleans up in the background - a wait while that happens is not a fault, as long as the process is continuing and completes. If the process halts leaving DS open that that is an issue, and the question becomes whether it is caused by DS itself or some other element (most obviously a third-party plug-in).
Simple: we have a litle bug :) look at it.
And worst, this bug is 'randomic'... really... some times happens, i dont know why. try look into :)
How do you deduce that? And in particular, how do you deduce where the bug is? Are you getting DS frozen (i.e. no CPU activity or memory use chnage) with no third-party plug-ins installed?
So this problem has been greatly exaggerated in 4.14. 4.12 usually cleared itself from memory within 10 minutes. 4.14 however, remains there indefinitely. I think the longest I've waited was close to 60 minutes and it was still there. Sometimes it only sits in memory, other times it uses the CPU as well, but it never actually closes.
Im having the same issue. Its not consistent but i have had problems with man fridays render que because of it, as it shuts down and re opend Daz Studio between renders, most of the time it does but every now and again ( and increasingly more frequently) it stalls.
Also ive just not been able to open daz studio a couple of times recently ( not having just closed it down ) and found it chndering along in the back ground.
I suspect there is a glitch somewhere in the software. It only seems to have been a thing for me since the last upadte.
If it's not using CPU, go to Windows>Panes(Tabs)>Aux Viewport, then from the option menu (the lined button in the top corner, or right-click the tab) deactivate the IPR Toolbar. You can then close the Aux Viewport again.
I don't know why or how, but doing this actually fixes the issue, even when it uses the CPU. After doing the steps it closes like the previous version in a few minutes.
Thank you for posting this, Richard!
I was having the same issue with 4.14, which started the other day. It wouldn't close even after setting overnight, I did update the nVidia driver to 457.30 on Friday, so I wonder if that may have caused it...
There's a fresh update to the Public Build of DS which has a permanent fix for the issue.
I upgraded the beta to 4.14.0.10 yesterday and had to exit both the release 4.14.0.8 and public beta 4.14.0.8 before doing so. On exit I opened the Task Manager and when to Details tab and ther both DS remained, release using 1.7GB RAM and DS PB using 6.6GB RAM. So anyway, while that was going on I was downloading all the new plugins & DS PB and by the time they finished downloading, less than 10 minutes, they had exiting on their own so I didn't have to use Task Manager to stop them. Last time I had to uninstall & reinstall after not checking that run status & installing the upgrades while still running. It partly hosed up the status of my CMS too regarding installs but I won't bother trying to remedy until I buy a new 2TB PCIe 3 NVMe SSD to split the contents of my current drive as fixing that is very time consuming.
Thank you, Richard. I'll check it out.
This, Sir, was priceless. Thank you so much!