Constant crashes on Mac
elegantscience
Posts: 0
Hello –
Been working in Daz for awhile but just joined the Forum to see if I can find any info on this issue.
For some reason with 4.12.1.117, and the newest Beta/Public Release, Daz crashes if I cancel a render, and sometimes even when I am saving a file. I'm losing a lot of painstaking work. Has anyone else experienced this? It's a gigantic drag. It's pretty much happening all the time. For instance last night I set the render to go all night to get the best quality. When I canceled this morning to save the render, Daz crashed and I lost an 8-hour, very nice render. Also seems to crash if I use the quick key for saving a file (command-S). There are so many crashes I might have to put Daz aside for awhile.
Has anyone experienced this?
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
Were you using shortcuts - cmd S, cmd R - or the menu commands (File>Save, Render>Render)?
Using no shortcuts with rendering. But save using command-S shortcut. Is that no longer supported by Daz? If not, I still have the render problem, which is the most significant in terms of lost work.
It is meant to be supported, but the release build at least has an issue with doubled reading which can cause problems - I thought that was fixed in the beta, but for now it may be best to try to avoid using shortcuts.
If that isn't the issue with rendering then I am not sure what it might be - especially if it is only intermittent.
Well, thanks for the guidance. In terms of the rendering problem, happens about 1 out of every 4 times I cancel a render.
I've been seeing this issue as well. Is there any point opening a bug ticket, or is this a known issue that is being worked on?
Crashing on cancel? I don't thibnk it's been widely reported on the forum so it may not have been ticketed either - opening one of your own is not a bad idea.
I'd say open a ticket, even if it has already been reported that might give them useful additional info.
It does seem to me that eschewing keyboard shortcuts somehow helps. I have a ticket filed on this. It took a while to find a repeatable case (on Catalina) for the ticket, and they still seem to be having trouble reproducing it.
Based on my observations, and a good deal of speculation, I have come to the conclusion that probably all the crashes are caused by the same bug. The 'crash on cancel' is a special case of this bug.
As Richard has said, avoiding command-key shortcuts should spare you almost all -- maybe even all -- the crashes. Obviously, this isn't ideal, but it's the only workaround we know of just now.
The issue seems to be that using a command-key shortcut puts a duplicate command into the command queue (or whatever DAZ uses for handling this type of event). So if you hit Cmd-O for Open, you will reliably get two Open dialogs; if you hit Cmd-R for Render, you'll get a dialog telling you the renderer is already in use (because Studio kicked off two render threads). If you hit Cmd-S for Save ... well, anything could happen. Where the real trouble starts is that the double-command issue puts Studio in an inconsistent state; it tries to start a 'save' thread when it's already in the middle of saving something. One thread will corrupt the memory being used by the other thread, and then it's "buckle up, Dorothy, because Kansas is about to go bye-bye." That's also probably why you get crash-on-cancel: quite probably, the cancel operation tries to dispose of a render thread that was already killed when you said 'OK' to the "Renderer already in use" dialog. The memory used by that thread has already been reclaimed or zero'ed, so trying to dispose of it a second time makes everything blow up.
The reason why the behavior is so random -- why, for instance, crash-on-cancel doesn't happen every time, why Cmd-S doesn't always destroy your original file (but it will sometimes; be very careful) -- is because of timing issues, or just the generally non-deterministic nature of program state. If Studio's trying to do operations on data structures that have been corrupted or invalidated, the contents of those structures might be almost anything, and the pointers they contain might point almost anywhere. So you get random behavior, and the only thing you can say with certainty is that It's Gonna Be Bad.
Hi,
I've already reported those bugs. Sometimes after the crash there is a r.jpg in the cache directory, which is the rendered file
I have the same problem with crashes when canceling renders on 4.12.1.117 - Mac Catalina 10.15.5
Looks like when you hit CMD+R Daz try to start two renderers... you cancel one, but might cause problem.
I tried Render to file (not window) and it crashed on cancel, but the render file was saved.
Will try avoiding shortcuts and wait for an update...
You might try the Public Build (beta), which installs alongside the general release https://www.daz3d.com/daz-studio-beta