Loading...
> >

daz studio crashes every time on startup. mac ventura

ChakradudeChakradude Posts: 258
in Daz Studio Discussion

Finally after months I got daz studio to install on my newish (2020) mac mini running Ventura. However now it crashes every time I try to start it up.

daz studio 4.21

 

Help Por favor!

I have attached the crash log

txt
txt
crash report.txt
38K

Comments

  • ChakradudeChakradude Posts: 258

    Daz studio crashes, not my computer LOL

  • PlatnumkPlatnumk Posts: 666

    Chakradude said:

    Finally after months I got daz studio to install on my newish (2020) mac mini running Ventura. However now it crashes every time I try to start it up.

    daz studio 4.21

     

    Help Por favor!

    I have attached the crash log

    Have you gone into MacOS's security settings & given Daz Full Disk Access? 

  • ChakradudeChakradude Posts: 258

    Platmumk thanks for your reply!

    as per your suggestion, I went ahead and enabled full disk access for daz studio and DIM. I noticed it runs just a bit more in the startup process before it once again crashes;(

     

    I put the report below again now the website is not letting me attach the full file

    weird

    Thanks!

    -------------------------------------
    Translated Report (Full Report Below)
    -------------------------------------

    Process:               DAZStudio [634]
    Path:                  /Applications/DAZ 3D/*/DAZStudio.app/Contents/MacOS/DAZStudio
    Identifier:            com.DAZ.DAZStudio
    Version:               4.21.0.5 (4.21.0.5)
    Code Type:             X86-64 (Translated)
    Parent Process:        launchd [1]
    User ID:               501

    Date/Time:             2023-02-03 15:50:55.3768 -0800
    OS Version:            macOS 13.1 (22C65)
    Report Version:        12
    Anonymous UUID:        3B7D0917-72C1-7866-FA71-6544F7FE0FED


    Time Awake Since Boot: 63 seconds

    System Integrity Protection: disabled

    Notes:
    dyld_process_snapshot_create_for_process failed with 5

    Crashed Thread:        0  Dispatch queue: com.apple.main-thread

    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000159b83ca0
    Exception Codes:       0x0000000000000001, 0x0000000159b83ca0

    Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
    Terminating Process:   exc handler [634]

    VM Region Info: 0x159b83ca0 is not in any region.  Bytes after previous region: 1621153  Bytes before following region: 2253664
          REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
          mapped file                 159969000-1599f8000    [  572K] r--/rwx SM=COW  ...t_id=a3894725
    --->  GAP OF 0x3b2000 BYTES
          __TEXT                      159daa000-159e81000    [  860K] r-x/rwx SM=COW  ...apbrush.dylib

    Error Formulating Crash Report:
    dyld_process_snapshot_create_for_process failed with 5

    Kernel Triage:
    VM - pmap_enter retried due to resource shortage
    VM - pmap_enter retried due to resource shortage
    VM - pmap_enter retried due to resource shortage
    VM - pmap_enter retried due to resource shortage
    VM - pmap_enter retried due to resource shortage


    Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
    0   QtCore                                   0x108a3aec4 QMetaObject::cast(QObject*) const + 34
    1   libdzcore.dylib                          0x10c55d602 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 8302242
    2   QtCore                                   0x108a34231 QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + 149
    3   QtGui                                    0x109c628a8 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 288
    4   QtGui                                    0x109c62b6d QApplication::notify(QObject*, QEvent*) + 655
    5   libdzcore.dylib                          0x10c461e5e DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 7272190
    6   QtCore                                   0x108a367e2 QCoreApplication::notifyInternal(QObject*, QEvent*) + 104
    7   QtCore                                   0x108a36bf3 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 593
    8   CoreFoundation                        0x7ff810f93ee1 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
    9   CoreFoundation                        0x7ff810f93e90 __CFRunLoopDoSource0 + 157
    10  CoreFoundation                        0x7ff810f93c5e __CFRunLoopDoSources0 + 212
    11  CoreFoundation                        0x7ff810f928b8 __CFRunLoopRun + 943
    12  CoreFoundation                        0x7ff810f91e8f CFRunLoopRunSpecific + 560
    13  HIToolbox                             0x7ff81ae1b766 RunCurrentEventLoopInMode + 292
    14  HIToolbox                             0x7ff81ae1b396 ReceiveNextEventCommon + 199
    15  HIToolbox                             0x7ff81ae1b2b3 _BlockUntilNextEventMatchingListInModeWithFilter + 70
    16  AppKit                                0x7ff814018f33 _DPSNextEvent + 909
    17  AppKit                                0x7ff814017db4 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1219
    18  QtGui                                    0x109c1ddb9 QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 1457
    19  QtCore                                   0x108a370dc QCoreApplication::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 78
    20  libdzcore.dylib                          0x10c4e3b3b DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 7803867
    21  libdzcore.dylib                          0x10c4e4975 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 7807509
    22  QtCore                                   0x108a4c131 QMetaObject::activate(QObject*, QMetaObject const*, int, void**) + 2001
    23  libdzcore.dylib                          0x10b92d36e DzScopeResolver::initIdentifierReplacements() + 405628
    24  libdzcore.dylib                          0x10c12018a DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 3856938
    25  libdzcore.dylib                          0x10c12695b DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 3883515
    26  libdzcore.dylib                          0x10c1278fd DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 3887517
    27  libdzcore.dylib                          0x10c127a5f DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 3887871
    28  libdzcore.dylib                          0x10c48ce24 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 7448260
    29  libdzcore.dylib                          0x10c490d46 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 7464422
    30  libdzcore.dylib                          0x10c490fd3 DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 7465075
    31  libdzcore.dylib                          0x10c4917aa DzFacetVertexSubPath DzFacetVertexSubPath::remapPath<signed char>(signed char, signed char const*) const + 7467082
    32  DAZStudio                                0x1000025dd main + 461
    33  DAZStudio                                0x100002304 start + 52

     

  • ChakradudeChakradude Posts: 258

    ok hadda be a txt file not RTF

    here goes:

    txt
    txt
    mac crash report.txt
    38K
  • PlatnumkPlatnumk Posts: 666

    Chakradude said:

    ok hadda be a txt file not RTF

    here goes:

     The only thing I can think off at this time is maybe a plug-in that you have installed is the culprit,  Perhaps try removing all installed Daz Plug-Ins see if it then runs without crashing.  If it does run without crashing then install each Plug-In one at a time then see if Daz crashes,  If it doesn't crash then install the next Plug-In etc.

  • ChakradudeChakradude Posts: 258

    Thanks!I was thinking that at some point acually but I forgot. I will try it and then I guess put a ticket in.

    I presume I just remove them all from the plugin folder? Otherwise Im not sure how...

  • ChakradudeChakradude Posts: 258

    Ha awsome! it started right up, took less than 10 seconds to open!

    now I gotta narrow it down...

    Thanks a bunch!

  • bytescapesbytescapes Posts: 1,841

    Chakradude said:

    now I gotta narrow it down...

    Those who grew up on System 7 (and earlier!) will remember the old routine for finding misbehaving extensions.

    Basically, remove half the plugins and try to start up. If you get a crash, the problem extension is in that group; divide the extensions in that group in half again, and try again until you've isolated the one that's causing the crash. If at any time you don't get a crash, switch in the other half and try with those.

    Of course in real life things can be more complicated because problems with extensions/plug-ins/etc. can be caused by a conflict between two (or more) of the extensions you're trying to troubleshoot. Then you can end up with a situation where all your groups function fine ... but as soon as you put them together again, stuff blows up.

    Computers!

  • tim_burrtim_burr Posts: 2

     

     

    I was having the same problem until I removed the UltraScenery plugin. Then Daz opened just fine. I still have an open ticket with Daz support and asked them to contact the developer.

  • mgriccio_967ba85463mgriccio_967ba85463 Posts: 3

    I am also on ventura, and i made a huge jump from a i7 imac running Mojave to a macmini m2 running ventura, and yes, there are crushes. It actually runs for me but the crashes occur frequently, mostly during rendering. Also, daz doesn't like it when I switch desktops or check the activity monitor! I tried 2 times to check how much ram daz was using and bam, it crashes.

    Daz Studio 4.10 on Mojave NEVER crashed... Hopefully this gets some attention.

  • PadonePadone Posts: 3,688
    edited May 2023

    At diffeomorphic we had issues with Ventura and Thomas had to work around some blender features to fit it.

    As I understand it Ventura is a very troublesome version. Many applications that worked fine with Big Sur stopped working with Ventura. Even compilers. So you can hope that Apple will fix it soon. Or you can try to downgrade.

    https://developer.apple.com/forums/thread/46466

    https://www.macworld.com/article/671318/how-to-downgrade-macos-revert-back.html

    Post edited by Padone on
  • wsterdanwsterdan Posts: 2,344
    edited May 2023

    mgriccio_967ba85463 said:

    I am also on ventura, and i made a huge jump from a i7 imac running Mojave to a macmini m2 running ventura, and yes, there are crushes. It actually runs for me but the crashes occur frequently, mostly during rendering. Also, daz doesn't like it when I switch desktops or check the activity monitor! I tried 2 times to check how much ram daz was using and bam, it crashes.

    Daz Studio 4.10 on Mojave NEVER crashed... Hopefully this gets some attention.

    Just out of curiousity, when you render do you tell it to render via the menu or palette, or do you hit <command-r>? If you're using keyboard commands for Render or Save, there have been problems off and on for a few versions causing crashes (luckily with Save it's after the save has been done).

    -- Walt Sterdan

    Post edited by wsterdan on
  • mgriccio_967ba85463mgriccio_967ba85463 Posts: 3
    edited July 2023

    wsterdan said:

    mgriccio_967ba85463 said:

    I am also on ventura, and i made a huge jump from a i7 imac running Mojave to a macmini m2 running ventura, and yes, there are crushes. It actually runs for me but the crashes occur frequently, mostly during rendering. Also, daz doesn't like it when I switch desktops or check the activity monitor! I tried 2 times to check how much ram daz was using and bam, it crashes.

    Daz Studio 4.10 on Mojave NEVER crashed... Hopefully this gets some attention.

    Just out of curiousity, when you render do you tell it to render via the menu or palette, or do you hit <command-r>? If you're using keyboard commands for Render or Save, there have been problems off and on for a few versions causing crashes (luckily with Save it's after the save has been done).

    -- Walt Sterdan

    Bingo! I don't why this is even a thing, but when I stopped using "Command R" the crashes have stopped. I had no crashes with Command S, for some reason. 

    Other than that, no issues. The app launches quickly, and renders of my old fairly complex files are WAY quicker. I still use 3delight out of necessity though and I haven't tested iray yet.

    Thank you! I would never have guessed something so dumb was causing problems and I would love to know why that is...

    BTW, using Daz3D 4.21.05

    Post edited by mgriccio_967ba85463 on
  • wsterdanwsterdan Posts: 2,344

    So glad that worked!

    The "Command-R" issue was supposedly resolved a version or two ago, but I guess it's still broken for some users, possibly related to OS version.

    Thanks for letting us know.

    -- Walt Sterdan

Sign In or Register to comment.