DAZ Studio won`t close. Will crash long after "closing"
Soto
Posts: 1,450
Hi!
I`ve been experiencing this weird issue since monthas ago, but I`m using DAZ Studio regularly right now, so it bacame more annoying.
Every time I close DAZ Studio, the closing process continues in the background for at least about 15 minutes, sometimes much more (hours in one occasion) before it returns a crash message. It happens every single time, regardless of what I was doing.
Someone had this before? I`m on a Mac, but not sure if that means something. I reinstalled, but nothing.
It`s really weird.
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
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
It will take a while to close if it had a large/complex scene loaded (takes best part of a minute with G3F loaded for me) but I haven't seen the crashing issue for a while - is this 4.9.3.166? Have you tried disabling third-party plug-ins (via Help>About Installed Plug-ins) and then, if that helps, reenabling them to find the issue?
I'm on a Mac, too, in particular an older one, so running 10.6.8 and DS4.8. I've just gotten to the point I make sure my scene is saved and then do a force quit.
Version is 4.9.3.166 yes, but I think the issue has been present at least in the previous version. If I open and close without loading or doing anything, it takes a couple of minutes, but just by loading Genesis 3 or doing something too basic, time increases ridiculously untill it finally crashes.
I will try disabling plug-ins, I don`t think I have anything third party right now, but will check, thanks.
I noticed similar behavior last night. Daz studio process kept using 6 gig ram long after I had closed it, I had to manually end the process to free up the ram.
Same issue here: running on 2013 MacBook Pro, system software all up to date. Seems that if I do *any* rendering, Daz Studio will hang on quit. Fresh reinstall of DS package using Install Manager didn't help.
Found a separate thread, discussing issues using DAZ Studio with the online Content Manager. Turns out that if I check "Work Offline" at the Welcome screen, DAZ Studio works perfectly well and closes quickly without hanging. (No more Force Quits on my Mac!) Hope this helps.
Thank you very much for that tip! I will try offline ASAP!
Ok so DAZ Studio might survive... but how about - nevermind,
I have that issue with 4.9.3.166 and previously with 4.8, too, for a long time and I am on the PC - Windows 7 computer.
And I mostly use "Work Offline", but it does not help with that issue - Daz Studio always crash on exit - even with the empty scene.
Only beta of Daz Studio works without any problem, so far.
A bit OT but it would be nice if anytime DS crashed and gave you a crash report it was in plain English that told you exactly what went wrong and not some indecipherable gobbledygook. ie, "..you ran out of memory buddy."
It happens every time on my older MacBook Pro. I'm definitely going to give it a shot using Work Offline...hopefully that will prevent the problem. I get concerned about routinely force-quitting the program as I don't know whether that could result in something getting corrupted on my system.
I use both a much newer Mac and a PC at work and never encounter this problem; neither are running the latest OS, but the hardware is 3-4 years newer. Perhaps the biggest factor though is that both systems have 64 GB RAM whereas my laptop has only 16.
Me too! I force quit or crash every time (had been for months) but will give that a try, thanks!
-- Walt Sterdan
Probably most disturbing is the "has been for months" and "since months ago" comments.
My DS was as solid as a rock until recently. I could hammer away for hours without any problems. But now it's unstable and has unpredictable crashes. Not a good sign and definately a big worry for me that there it now seems to have an uninvited ghost in it's shell.
People always assume it's Studio and not them or something else on their computer. My installation of Studio has been stable since the 4.5 days. Exits as you would expect and doesn't "crash".
While some crashes may be easy to diagnose most wouldn't be, after all with the exception of things like running out of memory if the developers knew of the issue they would fix it.
On my computer with Windows 7 64-bit, 32 GB of RAM, there is always C:\Program Files\DAZ 3D\DAZStudio4\QtCore4.dll
which gives ACCESS_VIOLATION
Qt is the application framework, so that coudl be many things. Is this crashing on exit, as in the original post, or during use?
Hi, Richard. It only happens on exit and as far as I remeber, it never happens while working or rendering in Daz Studio 4.9.3.166.
I have Daz Studio beta installed on the same computer and it never crashes on exit, even when rendering or working with it for hours.
The same QtCore4.dll is in the beta directory, so the problem lies somewhere else, probably in Daz Studio application itself,
but log file list only the entry point after the crash and that is the Qt application framework.
It is a bit strange, because these problems begin in Daz Studio 4.8, so I uninstalled it completely in hope to have it fixed in 4.9,
but so far have no luck with it.
I think, I have fixed my installation of Daz Studio. While looking at the Log file, I have spotted 2 errors:
2017-06-04 207 WARNING: dzneuraymgr.cpp(403):
Could not add path: "C:/Users/Artini/AppData/Roaming/DAZ 3D/Studio4/shaders/iray".
Due to unkown error -2
2017-06-04 207 WARNING: dzneuraymgr.cpp(403):
Could not add path: "C:/Users/Artini/AppData/Roaming/DAZ 3D/Studio4/temp/shaders/iray".
Due to unkown error -2
so, I have just created these 2 missing directories:
C:/Users/Artini/AppData/Roaming/DAZ 3D/Studio4/shaders/iray and C:/Users/Artini/AppData/Roaming/DAZ 3D/Studio4/temp/shaders/iray
and so far no crash on exit from Daz Studio 4.9.3.166. I am so happy to have fully working Daz Studio.
I have noticed, that C:/Users/Artini/AppData/Roaming/DAZ 3D/Studio4/temp/shaders/iray get deleted automatically
after run of Daz Studio and exit from it, but C:/Users/Artini/AppData/Roaming/DAZ 3D/Studio4/shaders/iray persists.
I've been getting this problem for the last month now too. I'm on a new iMac Pro, all latest software updates. When I press the Work Offline button, it also hangs for about 30 seconds, and the cursor freezes. After 30 seconds, it shows the login button and all is fine. When I quit, no more hang/unresponsive behavior, nor crashing... so far that is. I'm going to turn off auto-login too.
I had what sounds like the same problem a while back as discussed here,
https://www.daz3d.com/forums/discussion/160941/daz-started-crashing-everytime-i-close-it-solved#latest
For me It had something to do with my workspace layout. I reset my layout back to a previous saved layout and the problem went away. That fix also seemed to work for some other people in that thread as well.
Go to "window > workspace > select layout" and either try a different layout or delete your current layout if you have a custom saved layout and recreate it. Mine got corrupted somehow when I switched my monitors around and this fixed it. I haven't had the problem again since.
Greetings,
Yeah, this bug. Been getting it for years, only on Mac...generally with the betas. Embarassingly it's become common enough that I don't even report it, as it's usually fixed in the full release. (So I figure it's an artifact of the development release / beta process.)
The layout idea is a fascinating one, because it might just be that my beta and standard layouts are just the right amount different. (They're pretty substantially different, actually...don't know why I haven't made them look the same yet...)
-- Morgan
This still plagues me on an iMac Pro (previously a 2012 Mac Pro). But not always. When it does hang, it seems to be slowing to a crawl cleaning up resources. My scenes are very basic for now. Just a single G8 figure, eyelashes, brows, hair and few articles of clothing.
I did watch the Activity Monitor once and most RAM got re-collected when I triggered the quit (since no windows open) and seemed to free up anything that the renderer actually used (that does hit about 4 GB on average for me). Then it gets to about 900 MB of usage. Moments later, down to 700 MB. Sometimes I do lose my patience and just force-quit. Other times, the process cleans up in just about 2 to 3 seconds.
Details: 10-Core iMac Pro, 64 GB RAM, Vega 56 GPU (8 GB VRAM). macOS 10.13.3.
Side note: This never occurred with version 4.8. For 4.9, I would only get it when I launched the application for the first time, then attempted to quit. Would take sometimes about 5 minutes or so. Every launch of 4.9 after that, no issues when quitting. For 4.10 though, hit-or-miss.