Daz Studio crashes on launch on macOS Big Sur beta 9
georgewking
Posts: 0
I installed DazCentral and downloaded DazStudio on macOS Big Sur Beta 9 (11.0 Beta (20A5384c)). It crashes on launch; here is the OS generated crash report:
Process: DAZStudio [1028]
Path: /Users/USER/*/DAZStudio.app/Contents/MacOS/DAZStudio
Identifier: com.DAZ.DAZStudio
Version: 4.12.1.118 (4.12.1.118)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: DAZStudio [1028]
User ID: 501
Date/Time: 2020-10-03 12:14:28.600 -0400
OS Version: Mac OS X 10.16 (20A5384c)
Report Version: 12
Bridge OS Version: 3.0 (14Y908)
Anonymous UUID: 056AAA4C-6165-4A0D-ECAC-9C5698E8441D
Time Awake Since Boot: 1400 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD, [0x1] Library missing
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
dyld: No shared cache present
Library not loaded: /usr/lib/libstdc++.6.dylib
Referenced from: /Users/USER/*/DAZStudio.app/Contents/MacOS/DAZStudio
Reason: image not found
Binary Images:
0x100000000 - 0x100002fff +com.DAZ.DAZStudio (4.12.1.118 - 4.12.1.118) <DB6E293F-286F-9A4C-8B3C-B802AA52E3E1> /Users/USER/*/DAZStudio.app/Contents/MacOS/DAZStudio
0x100008000 - 0x102900fff +libdzcore.dylib (1) <5E5DD545-8AA5-FB74-248C-01BF0AA424C4> /Users/USER/*/libdzcore.dylib
0x102fc2000 - 0x103272fff +QtCore (4.8.7) <4CA3C606-A089-F187-979B-7B48C41EC059> /Users/USER/*/QtCore.framework/Versions/4/QtCore
0x103306000 - 0x103cd0fff +QtGui (4.8.7) <83428699-BE40-1D52-E6DE-D119AFD0A1B1> /Users/USER/*/QtGui.framework/Versions/4/QtGui
0x7fff68748000 - 0x7fff687e3fff dyld (832.5) <EB78B26D-29B3-3BA9-AC68-968C2AE40198> /usr/lib/dyld
Model: MacBookPro14,3, BootROM 428.0.0.0.0, 4 processors, Quad-Core Intel Core i7, 3.1 GHz, 16 GB, SMC 2.45f4
Graphics: kHW_IntelHDGraphics630Item, Intel HD Graphics 630, spdisplays_builtin
Graphics: kHW_AMDRadeonPro560Item, Radeon Pro 560, spdisplays_pcie_device, 4 GB
Memory Module: BANK 0/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320
Memory Module: BANK 1/DIMM0, 8 GB, LPDDR3, 2133 MHz, 0x802C, 0x4D5435324C31473332443450472D30393320
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x173), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1668)
Bluetooth: Version 8.0.0d54, 3 services, 27 devices, 1 incoming serial ports
Network Service: USB 10/100/1000 LAN, Ethernet, en7
Network Service: Wi-Fi, AirPort, en0
PCI Card: pci8086,15f0, sppci_usbxhci, Thunderbolt@196,0,0
USB Device: USB 3.1 Bus
USB Device: USB3.1 Hub
USB Device: Hub
USB Device: LG UltraFine Display Camera
USB Device: USB2.1 Hub
USB Device: Hub
USB Device: LG UltraFine Display Controls
USB Device: LG UltraFine Display Audio
USB Device: USB3.0 Hub
USB Device: USB 10/100/1000 LAN
USB Device: USB 3.0 Bus
USB Device: USB2.0 Hub
USB Device: Apple T1 Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 41.4
Thunderbolt Bus: MacBook Pro, Apple Inc., 41.4
Thunderbolt Device: UltraFine 5K, LG Electronics, 1, 43.1
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
I'll tell what I tell everyone on the Apple Beta program.
It's beta. you are testing it. no developer is racing to support changes in a beta when Apple still supports 3 other OS's at the time. When you agreed to test in the beta program you agreed to test a work-in-progress.
the error I'm guessing is possible due to apple changing the framework again in macOS11 which was done to consolidate macOS and iOS. Image not found could be a framework fail, in which case Daz developers need to know what changes Apple is sticking to in the API once macOS 11 is out of beta.
while this could be useful for developers at apple, and studio, and the purpose of beta is to bring things to light. I don't think it's going get fixed in this stage and as with any beta you are testing, not producing work. Probably report this to tech support.
Does this page help?
https://stackoverflow.com/questions/52488046/dyld-library-not-loaded-usr-lib-libstdc-6-dylib
And it (and DIM installer) keeps crashing on the release version. UnReal, Unity and Blender work. Well, back to old MacPro (since not even DIM works, I guess Daz is over for me on my new shining iMac).
Process: DAZStudio [11537]
Path: /Applications/DAZ 3D/*/DAZStudio.app/Contents/MacOS/DAZStudio
Identifier: com.DAZ.DAZStudio
Version: 4.14.0.8 (4.14.0.8)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: DAZStudio [11537]
User ID: 501
Date/Time: 2020-11-13 14:42:17.170 +0000
OS Version: macOS 11.0.1 (20B29)
Report Version: 12
Bridge OS Version: 5.0.1 (18P2561)
Anonymous UUID: 74B8C119-BD9B-A0F7-8BE1-83906B3368DB
Sleep/Wake UUID: 9EC388A0-5E92-4900-A428-3597EEABD936
Time Awake Since Boot: 2000 seconds
Time Since Wake: 1300 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD, [0x1] Library missing
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
dyld: No shared cache present
Library not loaded: /usr/lib/libstdc++.6.dylib
Referenced from: /Applications/DAZ 3D/*/DAZStudio.app/Contents/MacOS/DAZStudio
Reason: image not found
Binary Images:
0x100000000 - 0x100002fff +com.DAZ.DAZStudio (4.14.0.8 - 4.14.0.8) <4F7FBF35-311A-2CB6-6642-E30ABC171FFA> /Applications/DAZ 3D/*/DAZStudio.app/Contents/MacOS/DAZStudio
0x100006000 - 0x1028c4fff +libdzcore.dylib (1) <F70263D7-7F15-827E-FFB1-02EDAF558D7B> /Applications/DAZ 3D/*/libdzcore.dylib
0x102f89000 - 0x103239fff +QtCore (4.8.7) <4CA3C606-A089-F187-979B-7B48C41EC059> /Applications/DAZ 3D/*/QtCore.framework/Versions/4/QtCore
0x1032cd000 - 0x103c97fff +QtGui (4.8.7) <83428699-BE40-1D52-E6DE-D119AFD0A1B1> /Applications/DAZ 3D/*/QtGui.framework/Versions/4/QtGui
0x7fff5c2bc000 - 0x7fff5c357fff dyld (832.7.1) <2705F0D8-C104-3DE9-BEB5-B1EF6E28656D> /usr/lib/dyld
Model: iMac20,2, BootROM 1554.50.3.0.0 (iBridge: 18.16.12561.0.0,0), 10 processors, 10-Core Intel Core i9, 3,6 GHz, 48 GB, SMC
Graphics: kHW_AMDRadeonPro5700XTItem, AMD Radeon Pro 5700 XT, spdisplays_pcie_device, 16 GB
Memory Module: Slot 1 (Channel A / DIMM 1), 16 GB, DDR4, 2133 MHz, 85F7, J642GU42J9266NQ
Memory Module: Slot 2 (Channel A / DIMM 0), 8 GB, DDR4, 2133 MHz, SK Hynix, HMA81GS6DJR8N-VK
Memory Module: Slot 3 (Channel B / DIMM 1), 16 GB, DDR4, 2133 MHz, 85F7, J642GU42J9266NQ
Memory Module: Slot 4 (Channel B / DIMM 0), 8 GB, DDR4, 2133 MHz, SK Hynix, HMA81GS6DJR8N-VK
This is covered in the XCode 10 release notes.
DS is not, however, built with a recent version of XCode. The developers have, as I understand it, been maintaining backward compatibility (to OS 10.6) but the latest changes are requiring a consideration of options.
The software seems to use one of the XCode libraries, which since they don't use XCode is most likely why they didn't notice this library was about to disappear. The joy of Makefiles.
Yes, I misunderstood the message, I've updated my post - sorry for the contusion. I'm told that the update to the DS 4.5+ SDK has details.
Well, the good news is, now that I know you guys roll your own, I'm pretty sure I know why the program hangs on many machines on exit. I helped Poser diagnose something very similar.
does not start on mac OS SUR and it's not the beta version anymore
https://www.daz3d.com/forums/discussion/449316/daz-studio-4-14-pro-general-release/p1
Is this gonna be the same limbo Bryce fell into?
Considering that 4.14 came the same day as Big Sur after months of beta, the upcoming switch to Apple Silicon, the lack of support for nVidia GPUs in macOS, this incompatability really feels like a very bad omen.
I really would like to know if Daz Studio has a future on the Mac. This is important to me.
The issue is balancing compatibility with Big Sur against compatibility with older versions. Daz can estimate from customer service tickets which versions of MacOSX are being used, and must decide whether supporting Big Sur is worth dropping support for older versions. It's the same issue as deciding when to update Iray to support newer GPUs at the cost of dropping support for older GPUs.
The library switch happened 4 years ago.
And I'm using an eight years old Mac. So?
Sigh my bad luck, i had just decided to adopt Daz Studio, bought some pro models. Did the Big Sur update...a few audio plugins no longer work and Daz Studio!
All we can do is tell you to keep an eye on the change log - I'm expect any adjustments will be noted there.
My point is, there should be some communication on the matter, whatever the decision is and the reasoning behind it.
Alot of MAC users waking up to disappointment in knowing they can't use DAZ STUDIO. Poor planning on the Developers part. They knew what was coming.
It is something Daz has been working on. One issue is that the changes needed will chnage the ABI, which is in effect the SDK - plug-ins will then break on both platforms, which will be a significant issue for users of several that will not be recompiled or rewritten on both platforms.
I understand the problem but the information that the library that is causing all these problems would be deprecated and removed from the system is old (like four years old).
And fixing it will, I gather, kill things like GenX stone dead. Daz has to weigh the interests of different groups, and look at possible ways forward.
but, like, we just got a new beta update with 12.9. we got filament with that, right? Why not wait to do all this other stuff until it's fixed? Or, give people a way to rollback? (if there is one, lemme know, because even though I'm on a PC I'm getting less stability than with 12.9)
Big Sur is no longer a beta product - DAZ continues to crash on startup. There were issues with the introduction of OS Catalina (Daz could not read/load recent saves). While I have invested significantly in DAZ assets, it is time to investigate alternatives to DAZ Studio. I choose Mac for a number of reasons. In my opinion, the developers of the DAZ platform do not see Mac uses as an important contingency. These types of issues are introduced with every new MacOS launch -- as if they don't take the time to load the available beta releases and remediate issues prior to production release. Additionally, the total lack of high performance rendering support for anything other than intel GPU's (re: Radeon for example) is a clear indication that they are perfectly satisfied with the Intel/Windows User community. The search is on - anyone have any suggestions for a replacement that pays equal attention to the MacOS product line?
Big Sur is no longer a beta product - DAZ continues to crash on startup. There were issues with the introduction of OS Catalina (Daz could not read/load recent saves). While I have invested significantly in DAZ assets, it is time to investigate alternatives to DAZ Studio. I choose Mac for a number of reasons. In my opinion, the developers of the DAZ platform do not see Mac uses as an important contingency. These types of issues are introduced with every new MacOS launch -- as if they don't take the time to load the available beta releases and remediate issues prior to production release. Additionally, the total lack of high performance rendering support for anything other than intel GPU's (re: Radeon for example) is a clear indication that they are perfectly satisfied with the Intel/Windows User community. The search is on - anyone have any suggestions for a replacement that pays equal attention to the MacOS product line?
As noted above, addressing this crash will have serious negative consequences beyond Mac users.
Daz does not code Iray and has no way to enforce nVidia, its developers, to support alternative GPUs. Mac users have been the victims of a falling out between two companies, which has reached its culmination in the complete inability to use GPU acceleration. the situation was not so dire when Daz adopted Iray.
There's a catch here, which is that if Studio users decide not to upgrade to Big Sur because it isn't compatible with DAZ Studio, DAZ will just say "Ah, no one's using Big Sur, we don't need to support it." But many Mac users will still have a real interest in using Big Sur.
Richard suggests that this is a consequence of Apple's spat with Nvidia and that Iray is the root problem -- which is certainly what I'd have assumed -- but other posts in the thread seem to imply that it's a different issue. Interesting. Although I imagine that even if it's not Iray this time around, there'll be trouble in future on the new M1 Macs. I can't imagine that CPU rendering -- which seems to rely on code generated dynamically for Intel CPUs -- will run smoothly or quickly under real-time transpilation for an ARM architecture. That just sounds like a recipe for pain.
It's not an Iray issue. Updating for Big Sur will break the API's, so all plugins will need to be recompiled, which means some will be lost. This is the same reason Daz Studio has not been updated to QT5. That doesn't mean these aren't being worked on -- they are and have been for a long time -- but making the switchover is a big step. I'm sure Big Sur has increased the pressure to make the jump, but everyone is going to be majorly affected by it, and a lot of them are going to be unhappy with the change.
No i didn't - I was adderssing a different aspect of the post I was replying to when I mentioned Iray. The issue with Big sur, as I understand it, is that making the changes needed to produce a version of DS compatible with the new version will break the existing SDK, requiring developers to recompile their plug-ins for both mac and Windows (and since some developers have left or dies, leaving some plug-ins inoperative for all users).
Please note there has never been a better time to use Blender with new export options.
Apologies. I didn't read carefully enough.
I guess the question now is: which plugins will break and can't be recompiled, and is the base of potential users of those plugins larger or smaller than the potential users of Big Sur? I would guess that if the SDK changes only affected Mac users, then it would make sense to break the plugins ... but if changing the SDK affects Windows users as well then the numbers probably don't favor making the breaking change. Which means no DAZ-on-Big-Sur for us.