Kontakt crashing in Logic [en-us]

Answered

Comments

5 comments

  • Avatar
    N/A N/A

    I am now also getting crashes in Logic after using Kontakt, if I continue working on a project after the notes disappear. Before it crashes, the menu bars become strange question marks, like this:

    I am starting to think that this is a Logic issue, as I just updated to 10.4.4 a few days ago. Logic says it crashed using Kontakt though? I can email a crash report if that may be helpful.

    Thanks!

    0
    Comment actions Permalink
  • Avatar
    Chris @ NI

    Hello Jonathan,

    We're not seeing reports of this by other users so far, but here a couple of things you can try:

    1. As a test, open Kontakt as a standalone application and load your sample modeling instruments. Let Kontakt sit and see if you get the error that a sample has disappeared. If you don't get that error with the standalone application, then this might be an issue with Logic 10.4.4. If you have a backup or download link for 10.4.3, it might be worth downgrading if you don't remember this issue happening before you updated to 10.4.4.

     

    2. Please try the following steps with all audio applications closed:

    1. From the Finder, hold Shift+Command+G

    2. In the window that appears, type or copy and paste the following text:
    ~/Library/Application Support/Native Instruments/

    3. Move the Kontakt 5 folder to the trash.

    4. Again, hold Shift+Command+G

    5. In the window that appears, type or copy and paste the following text:
    ~/Library/Preferences/

    6. Move the file called "com.native-instruments.Kontakt 5.plist" to the trash.

    7. Empty the trash and then restart your computer.

    8. After your computer restarts, open Kontakt 5 as a standalone application for a few seconds and then close it. Next, open Logic and see if you still get a crash.

    0
    Comment actions Permalink
  • Avatar
    N/A N/A (Edited )

    Hi Chris,

    Thanks very much for your suggestions, and apologies that I have taken so long to get back to you - I have been away for a few weeks without access to my DAW.

    Unfortunately I no longer have Logic 10.4.3 so cannot roll back to a previous versions - and all the other Logic users that I know personally have had Logic auto-updated and so I cannot get the file from them either.

    I have tested Kontakt standalone and it works, I haven't had the error message there.

    I tried your second suggestion also, but unfortunately this made no difference.

    I also tried relocating my samples to a different, faster SSD, but this also made no difference within Logic - still just kontakt note drop outs that increase with time before crashing. The Logic instrument icons are sometimes also disappearing when this happens before the crash, which is very odd.

    I am going to attempt to contact apple as well to see if they have encountered this problem before.

    Cheers,

    Jon

    0
    Comment actions Permalink
  • Avatar
    N/A N/A

    I spoke with Apple support today, who were very helpful. The support guy that I spoke with said that this was the relevant section of the Logic crash report (below). I am paraphrasing here (as I don't understand it well), but he said that the problem is coming from Kontakt assigning memory overlapping with other programs. He said it was called buffer overflow, and that because it is using RAM it shouldn't be using it can interfere with other programs, which would explain Logic's strange behaviour and crashes.

     

    Thread 57 Crashed:

    0   libsystem_kernel.dylib        0x00007fff61bd9b66 __pthread_kill + 10

    1   libsystem_pthread.dylib       0x00007fff61da4080 pthread_kill + 333

    2   libsystem_c.dylib             0x00007fff61b3524d __abort + 144

    3   libsystem_c.dylib             0x00007fff61b351bd abort + 142

    4   libc++abi.dylib               0x00007fff5fa2ff8f abort_message + 245

    5   libc++abi.dylib               0x00007fff5fa30113 default_terminate_handler() + 241

    6   libobjc.A.dylib               0x00007fff60e71eab _objc_terminate() + 105

    7   libc++abi.dylib               0x00007fff5fa4b7c9 std::__terminate(void (*)()) + 8

    8   libc++abi.dylib               0x00007fff5fa4b26f __cxa_throw + 121

    9   Kontakt.MusicDevice.component 0x0000000148e36215 void boost::throw_exception<boost::exception_detail::error_info_injector<boost::uuids::entropy_error> >(boost::exception_detail::error_info_injector<boost::uuids::entropy_error> const&) + 181

    10  Kontakt.MusicDevice.component 0x0000000148e36106 void boost::exception_detail::throw_exception_<boost::uuids::entropy_error>(boost::uuids::entropy_error const&, char const*, char const*, int) + 102

    11  Kontakt.MusicDevice.component 0x0000000148e3607d boost::uuids::detail::random_provider_base::random_provider_base() + 157

    12  Kontakt.MusicDevice.component 0x0000000148e11c9a NI::GP::UUID::generateRandom() + 26

    13  Kontakt.MusicDevice.component 0x0000000148a08bf0 ni::uret::ident::generateUserIdAlias() + 80

    14  Kontakt.MusicDevice.component 0x0000000148a07d15 ni::uret::WorkerThread::sendAliasEvent() + 277

    15  Kontakt.MusicDevice.component 0x0000000148a07056 ni::uret::WorkerThread::track() + 38

    16  Kontakt.MusicDevice.component 0x0000000148a06ddc ni::uret::WorkerThread::main() + 604

    17  Kontakt.MusicDevice.component 0x0000000148a3c171 void* std::__1::__thread_proxy<std::__1::tuple<std::__1::__bind<void (ni::uret::WorkerThread::*)(), ni::uret::WorkerThread*> > >(void*) + 113

    18  libsystem_pthread.dylib       0x00007fff61da1661 _pthread_body + 340

    19  libsystem_pthread.dylib       0x00007fff61da150d _pthread_start + 377

    20  libsystem_pthread.dylib       0x00007fff61da0bf9 thread_start + 13

    0
    Comment actions Permalink
  • Avatar
    Chris @ NI

    I've forwarded this the Kontakt team to try to get some further information. I will get back to you as soon as I have more information from them. As of now though, I am unable to reproduce these issues on any of my systems.

    0
    Comment actions Permalink

Post is closed for comments.