Kontakt seems to be responsible for the crash according to the Digital Performer crash log. After launching Digital Performer I get a pop up message with the choice to relaunch, ignore or send the crash log to Apple. Note that if I click Ignore, Digital Performer continues to work without problem. Can someone enlighten me on this crash? What is the reason and possibly the solution to this crash? ============================ Crash log beginning: Process: Digital Performer [1852] Path: /Applications/Digital Performer.app/Contents/MacOS/Digital Performer Identifier: com.motu.DigitalPerformer Version: 11.36 (11.36) Code Type: ARM-64 (Native) Parent Process: Digital Performer [1806] Responsible: Digital Performer [1806] User ID: 501 Date/Time: 2026-02-09 13:31:18.0124 -0500 OS Version: macOS 15.7.3 (24G419) Report Version: 12 Anonymous UUID: 4BFF90B9-803D-E6AB-A93A-C60848F2D6BA Time Awake Since Boot: 210 seconds System Integrity Protection: enabled Crashed Thread: 0 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x000000019cb6fd88 Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5 Terminating Process: exc handler [1852] Application Specific Information: crashed on child side of fork pre-exec Thread 0 Crashed: 0 libsystem_malloc.dylib 0x19cb6fd88 + 0 1 libsystem_malloc.dylib 0x19cb39c90 tiny_malloc_from_free_list + 1900 2 libsystem_malloc.dylib 0x19cb38dc4 tiny_malloc_should_clear + 272 3 libsystem_malloc.dylib 0x19cb37be8 szone_malloc_should_clear + 84 4 libsystem_collections.dylib 0x1aaf79da8 os_set_32_ptr_init + 108 5 libsystem_notify.dylib 0x1a0ca03e8 0x1a0c9a000 + 25576 6 libsystem_notify.dylib 0x1a0ca0da8 notify_fork_child + 248 7 libSystem.B.dylib 0x1aaf965b0 libSystem_atfork_child + 60 8 libsystem_c.dylib 0x19cbeb3f0 fork + 112 9 Kontakt 8 0x475b1f1b8 boost::process::v1::detail::posix::executor , boost::process::v1::detail::set_on_error>, boost::fusion::filter_view const, boost::process::v1::detail::is_initializer >>>>::invoke(mpl::bool_ , mpl_::bool_ ) + 1260 10 Kontakt 8 0x475b1dae8 boost::process::v1::child boost::process::v1::detail::basic_execute_impl (boost::filesystem::path&&, char const (&) [3], boost::filesystem::path&, std::_1::error_code&, boost::process::v1::detail::posix::sig_init&&) + 244 11 Kontakt 8 0x475b1d7d8 boost::process::v1::child::child (boost::filesystem::path&&, char const (&) [3], boost::filesystem::path&, std::_1::error_code&, boost::process::v1::detail::posix::sig_init&&) + 48 12 Kontakt 8 0x475b1d6b0 int boost::process::v1::detail::system_impl (std::__1::integral_constant , std::__1::integral_constant , boost::filesystem::path&&, char const (&) [3], boost::filesystem::path&, std::__1::error_code&) + 52 13 Kontakt 8 0x475b1d1d4 ni::odr::ipc::start_agent() + 440 14 Kontakt 8 0x475b4612c ni::odr::ipc::kks::ipc_client_core::connect(strong::type ) + 92 15 Kontakt 8 0x475b336c4 boost::asio::detail::binder0 >)>, strong::type )::$_4>::operator()() + 88 16 Kontakt 8 0x475b36ac4 boost::asio::detail::executor_op >)>, strong::type )::$_4>, std::__1::allocator , boost::asio::detail::scheduler_operation>::do_complete(void*, boost::asio::detail::scheduler_operation*, boost::system::error_code const&, unsigned long) + 292 17 Kontakt 8 0x476b72960 boost::asio::detail::scheduler::do_run_one(boost::asio::detail::conditionally_enabled_mutex::scoped_lock&, boost::asio::detail::scheduler_thread_info&, boost::system::error_code const&) + 756 18 Kontakt 8 0x476b6d348 boost::asio::detail::scheduler::run(boost::system::error_code&) + 204 19 Kontakt 8 0x476b6d22c boost::asio::io_context::run() + 32 20 Kontakt 8 0x475b2f3cc void* std::__1::__thread_pr

Home
Kontakt

Digital Performer 11.38 quit unexpectedly

Kontakt seems to be responsible for the crash according to the Digital Performer crash log.
After launching Digital Performer I get a pop up message with the choice to relaunch, ignore or send the crash log to Apple.
Note that if I click Ignore, Digital Performer continues to work without problem.
Can someone enlighten me on this crash?
What is the reason and possibly the solution to this crash?

============================

Crash log beginning:

Process: Digital Performer [1852]
Path: /Applications/Digital Performer.app/Contents/MacOS/Digital Performer
Identifier: com.motu.DigitalPerformer
Version: 11.36 (11.36)
Code Type: ARM-64 (Native)
Parent Process: Digital Performer [1806]
Responsible: Digital Performer [1806]
User ID: 501

Date/Time: 2026-02-09 13:31:18.0124 -0500
OS Version: macOS 15.7.3 (24G419)
Report Version: 12
Anonymous UUID: 4BFF90B9-803D-E6AB-A93A-C60848F2D6BA

Time Awake Since Boot: 210 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x000000019cb6fd88

Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5
Terminating Process: exc handler [1852]

Application Specific Information:
crashed on child side of fork pre-exec

Thread 0 Crashed:
0 libsystem_malloc.dylib 1 libsystem_malloc.dylib 2 libsystem_malloc.dylib 3 libsystem_malloc.dylib 4 libsystem_collections.dylib 5 libsystem_notify.dylib 6 libsystem_notify.dylib 7 libSystem.B.dylib 8 libsystem_c.dylib 9 Kontakt 8 10 Kontakt 8 11 Kontakt 8 12 Kontakt 8 13 Kontakt 8 14 Kontakt 8 15 Kontakt 8 16 Kontakt 8 17 Kontakt 8 18 Kontakt 8 19 Kontakt 8 20 Kontakt 8 0x19cb6fd88 <deduplicated_symbol> + 0
0x19cb39c90 tiny_malloc_from_free_list + 1900
0x19cb38dc4 tiny_malloc_should_clear + 272
0x19cb37be8 szone_malloc_should_clear + 84
0x1aaf79da8 os_set_32_ptr_init + 108
0x1a0ca03e8 0x1a0c9a000 + 25576
0x1a0ca0da8 notify_fork_child + 248
0x1aaf965b0 libSystem_atfork_child + 60
0x19cbeb3f0 fork + 112
0x475b1f1b8 boost::process::v1::detail::posix::executor<boost::fusion::joint_view<boost::fusion::tuple<boost::process::v1::detail::posix::exe_cmd_init<char>, boost::process::v1::detail::set_on_error>, boost::fusion::filter_view<boost::fusion::tuple<boost::filesystem::path&, char const (&) [3], boost::filesystem::path&, std::1::error_code&, boost::process::v1::detail::posix::sig_init&> const, boost::process::v1::detail::is_initializer<mpl::arg<-1>>>>>::invoke(mpl::bool_<false>, mpl_::bool_<false>) + 1260
0x475b1dae8 boost::process::v1::child boost::process::v1::detail::basic_execute_impl<char, boost::filesystem::path, char const (&) [3], boost::filesystem::path&, std::_1::error_code&, boost::process::v1::detail::posix::sig_init>(boost::filesystem::path&&, char const (&) [3], boost::filesystem::path&, std::_1::error_code&, boost::process::v1::detail::posix::sig_init&&) + 244
0x475b1d7d8 boost::process::v1::child::child<boost::filesystem::path, char const (&) [3], boost::filesystem::path&, std::_1::error_code&, boost::process::v1::detail::posix::sig_init>(boost::filesystem::path&&, char const (&) [3], boost::filesystem::path&, std::_1::error_code&, boost::process::v1::detail::posix::sig_init&&) + 48
0x475b1d6b0 int boost::process::v1::detail::system_impl<boost::asio::io_context, boost::filesystem::path, char const (&) [3], boost::filesystem::path&, std::__1::error_code&>(std::__1::integral_constant<bool, false>, std::__1::integral_constant<bool, false>, boost::filesystem::path&&, char const (&) [3], boost::filesystem::path&, std::__1::error_code&) + 52
0x475b1d1d4 ni::odr::ipc::start_agent() + 440
0x475b4612c ni::odr::ipc::kks::ipc_client_core::connect(strong::type<bool, ni::odr::ipc::kks::agent_autostart_tag>) + 92
0x475b336c4 boost::asio::detail::binder0<ni::odr::ipc::kks::ipc_client::connect_to_agent(std::__1::function<void (tl::expected<void, std::__1::variant<std::__1::error_code, ni::msgpack_rpc::msgpack_rpc_host_error>>)>, strong::type<bool, ni::odr::ipc::kks::agent_autostart_tag>)::$_4>::operator()() + 88
0x475b36ac4 boost::asio::detail::executor_op<boost::asio::detail::binder0<ni::odr::ipc::kks::ipc_client::connect_to_agent(std::__1::function<void (tl::expected<void, std::__1::variant<std::__1::error_code, ni::msgpack_rpc::msgpack_rpc_host_error>>)>, strong::type<bool, ni::odr::ipc::kks::agent_autostart_tag>)::$_4>, std::__1::allocator<void>, boost::asio::detail::scheduler_operation>::do_complete(void*, boost::asio::detail::scheduler_operation*, boost::system::error_code const&, unsigned long) + 292
0x476b72960 boost::asio::detail::scheduler::do_run_one(boost::asio::detail::conditionally_enabled_mutex::scoped_lock&, boost::asio::detail::scheduler_thread_info&, boost::system::error_code const&) + 756
0x476b6d348 boost::asio::detail::scheduler::run(boost::system::error_code&) + 204
0x476b6d22c boost::asio::io_context::run() + 32
0x475b2f3cc void* std::__1::__thread_pr

Find more posts tagged with

Apple Silicon

Accepted answers

Jeremy_NI

https://community.native-instruments.com/discussion/comment/256774#Comment_256774

Unfortunately we can't recommend this or that model, as we haven't tested it in house and it's not just about the MK3 keyboard in your case. Maybe it doesn't need to be that expensive. Bringing external power to the devices instead of them being powered by your Mac should improve the situation anyway.

All comments

Jeremy_NI

Have you tried to open Kontakt in standalone? Does it crash as well? Have you tried these steps? Kontakt Crashes

JazzHot

Kontakt is not crashing!
Kontakt makes performer crash according to the log.

Also here is the pop up message I get when the crash happens.
It is in french! I'm sorry. But here is the translation:
"Digital Performer has quit unexpectedly"

DP quit unexpectedly.png

Jeremy_NI

https://community.native-instruments.com/discussion/comment/256372#Comment_256372

Performing the steps in the article can also work in this case. Deleting the plist will reset Kontakt to default, in all formats.

How do the crashes happen? When loading a Kontakt instance, when loading an instrument? Can you describe step by step the events leading to the crash?

JazzHot

Here is what I found out….

The cause of the problem seems to be the Kontrol s49 MK3 keyboard and the computer booth sequence.

Explanation:

The MK3 keyboard is plugged into a USB C port of my Studio M2
If the ON/OFF switch of the MK3 is set to ON (back of the MK3 keyboard) shutting down the computer shut down the MK3 also.

Powered by USB C connexion, the MK3 is automatically detected during a computer booth sequence.
The computer booth sequence seems to cause the crash problem.

Solution:

Before boothing the computer, I set the ON/Off switch of the MK3 keyboard to OFF and then I booth the computer.
The MK3 keyboard is therefore not detected.

Once the boothing is finished, I set the ON/OFF switch of the MK3 keyboard to ON and launch Digital Performer.
No more crashing !!!!!
In the mean time, i will manually set the MK3 keyboard to OFF (physical ON/OFF switch) after a computer shutdown and set it to ON, only after a completed booth of the computer then launch Digital Performer.

For the next few days, I will do some more testing to make sure but so far so good.

DunedinDragon

One thing you might look at which I had to do with my MK3 keyboard is my computer wasn't providing adequate power levels to my MK3 through the USB connectionfrom my computer and was causing intemittent inconsistencies. I used an old plugin power wart for a laptop with a USB C output (checking it was consistent with the input levels required by the MK3) and all the inconsistencies went away.

JazzHot

@DunedinDragon
Thanks for your help.
Mac Studio M2 USB-C port provide enough power according to the specs.
Also, the MK3 works flawlessly in any other DAW.

After more testing, the MK3 is not the source of the problem neither the booting sequence.
I only have this problem with Digital Performer 11.

So back to square one with the problem…

Jeremy_NI

https://community.native-instruments.com/discussion/comment/256542#Comment_256542

Oh ok, but Kontakt is still the culprit? Can you share a recent crashlog (txt format) and post it here?

JazzHot

The culprit of my Digital Performer crash notification is my audio interface which is a Neumann MT48 !!!

The MT48 has a booting time of around 90 seconds and this what cause the crash problem I have with Digital Performer.

Let me explain the booting sequence I used to avoid the Digital Performer crash notification.

1- I make sure that my Control S49 MK3 keyboard ON/OFF switch is set to OFF

2- Fire up ONLY the MT48 interface and wait it finishes completely it's booting procedure

3- Fire up the Mac Studio M2 and wait it finishes the booting process

4- Then fire up the MK3 (set the ON/OFF switch to ON)

5- Launch Digital Performer

I think that the MT48 booting duration screws the computer booting process (maybe a cache or memory glitch, I don't know... this goes beyond my knowledge.

One thing for sure, NO MORE CRASH if using the booting sequence above.

Jeremy_NI

https://community.native-instruments.com/discussion/comment/256726#Comment_256726

I remember seeing issues reported with these Mac Studios and the USB C ports being problematic regarding power distribution, including with our mk3 keyboards. Have you tried other ports on the computer? Also worth mentioning that the issues with our keyboards were fixed on these Macs by using a powered usb C hub: Kontrol S-Series MK3: Avoiding Connection Issues by Using the Right USB-C Hubs and Cables

JazzHot

I will get a powered USB C hub.
The problem persist even after booting like explained in my previous message.
I will report back.

Thanks

JazzHot

Do this hub a good choice?

CBelkin Connect Thunderbolt 4 Docking Station, 5-in-1 USB-C Multiport Core Hub w/ 96W Power Delivery for Mac, Windows, Single 8K or Dual 4K Display, Thunderbolt 4 Cable & Power Supply Included

Jeremy_NI

https://community.native-instruments.com/discussion/comment/256774#Comment_256774

Quick links

Unanswered questions