coastcj Posted January 14, 2021 Share Posted January 14, 2021 I've been experiencing a problem for over a year now, and I am wondering if anyone can offer guidance. Occasionally, but not always, Logic will quit when opening a session and list an offending 3rd party plugin, e.g. Native Instruments Replika, or Waves CLA, etc... I have included a partial example error report below (sorry, couldn't attach txt file to msg). Note that although it happens on many 3rd party manufacturers, I did send to N.I. anyway but they couldn't figure it out (I wouldn't expect them too, but was hoping) WORKAROUND: If I ignore the error, open a blank session, instantiate the offending plug-in, it loads fine, and then close this blank session (but DO NOT QUIT LOGIC) and REOPEN the original session that quit unexepectedly it will also open without issue. If I quit Logic, then re-open session this workaround fails. This workaround is why I put up with the problem since 10.2 or so, but now with bigger sessions and working on several sessions per week, it's become a good 7- 10 minute delay just to get my original session going. I have tried all the usual things (reinstalling the plug-ins, deleting the plist perferences, caches, etc... even reformatted hard drive) to no avail I'm on Catalina now, but this predates Catalina and goes back at least 2 OS ago. Thanks, {\rtf1\ansi\ansicpg1252\cocoartf2513 \cocoatextscaling0\cocoaplatform0{\fonttbl\f0\fswiss\fcharset0 Helvetica;} {\colortbl;\red255\green255\blue255;} {\*\expandedcolortbl;;} \margl1440\margr1440\vieww10800\viewh8400\viewkind0 \pard\tx720\tx1440\tx2160\tx2880\tx3600\tx4320\tx5040\tx5760\tx6480\tx7200\tx7920\tx8640\pardirnatural\partightenfactor0 \f0\fs24 \cf0 Process: Logic Pro X [1311]\ Path: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X\ Identifier: com.apple.logic10\ Version: 10.6.1 (5415)\ Build Info: MALogic-5415000000000000~2 (10U119)\ App Item ID: 634148309\ App External ID: 839116456\ Code Type: X86-64 (Native)\ Parent Process: ??? [1]\ Responsible: Logic Pro X [1311]\ User ID: 501\ \ PlugIn Path: /Library/Audio/Plug-Ins/Components/Replika XT.component/Contents/MacOS/Replika XT\ PlugIn Identifier: Replika XT.MusicDevice.component\ PlugIn Version: 1.1.0 [R47] (1.1.0 [R47], Copyright \'a9 2020 Native Instruments GmbH)\ \ Date/Time: 2021-01-14 13:47:29.350 -0800\ OS Version: Mac OS X 10.15.7 (19H2)\ Report Version: 12\ Bridge OS Version: 4.6 (17P6610)\ Anonymous UUID: 2EB92305-0AFA-542D-FF1F-161F1A5A2DE9\ \ \ Time Awake Since Boot: 6000 seconds\ \ System Integrity Protection: enabled\ \ Crashed Thread: 0 Dispatch queue: com.apple.main-thread\ \ Exception Type: EXC_BREAKPOINT (SIGTRAP)\ Exception Codes: 0x0000000000000001, 0x0000000000000000\ Exception Note: EXC_CORPSE_NOTIFY\ \ Termination Signal: Trace/BPT trap: 5\ Termination Reason: Namespace SIGNAL, Code 0x5\ Terminating Process: exc handler [1311]\ \ Application Specific Information:\ Dublin | 6b34edbe1e2428234532a9a90f0dda622834cd344de3e01f645f6cf5be04bce1 | 6929e9fa277a970fca0074748e47266d4dfd6072 | 2020-12-07_19:05:26\ \ \ Thread 0 Crashed:: Dispatch queue: com.apple.main-thread\ 0 Replika XT.MusicDevice.component 0x0000000129744e93 void boost::movelib::op_merge_with_left_placed, std::__1::allocator > >, std::__1::basic_string, std::__1::allocator >, boost::move_detail::identity, std::__1::allocator > > >, boost::movelib::move_op, std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*>(std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*, boost::container::dtl::flat_tree_value_compare, std::__1::allocator > >, std::__1::basic_string, std::__1::allocator >, boost::move_detail::identity, std::__1::allocator > > >, boost::movelib::move_op) + 275\ 1 Replika XT.MusicDevice.component 0x000000012974289f void boost::movelib::adaptive_merge, std::__1::allocator >*, boost::container::dtl::flat_tree_value_compare, std::__1::allocator > >, std::__1::basic_string, std::__1::allocator >, boost::move_detail::identity, std::__1::allocator > > > >(std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*, std::__1::basic_string, std::__1::allocator >*, boost::container::dtl::flat_tree_value_compare, std::__1::allocator > >, std::__1::basic_string, std::__1::allocator >, boost::move_detail::identity, std::__1::allocator > > >, boost::movelib::iterator_traits, std::__1::allocator >*>::value_type*, boost::movelib::iterator_traits, std::__1::allocator >*>::size_type) + 671\ Quote Link to comment Share on other sites More sharing options...
des99 Posted January 14, 2021 Share Posted January 14, 2021 This sounds like it could be the Pace bug that's been reported multiple times here. Do you use any plugins that use Pace/iLok? (either HD authorised, or on a physical USB iLok) (It doesn't have to be iLok plugins that are crashing, the plugin crashes appear random and with different plugins, even non-iLok ones.) Quote Link to comment Share on other sites More sharing options...
coastcj Posted January 14, 2021 Author Share Posted January 14, 2021 Wow, yes I do - and didn't think of that because Waves and NI are not iLok and I use them the most. Thanks for at least giving me a new place to look, I appreciate it! Quote Link to comment Share on other sites More sharing options...
coastcj Posted January 14, 2021 Author Share Posted January 14, 2021 I did just login and try a session I know crashes every time and it still crashes after iLok software update - so either they didn't fix it yet, or this isn't my issue. nonetheless, I'll keep looking. thanks again Quote Link to comment Share on other sites More sharing options...
des99 Posted January 14, 2021 Share Posted January 14, 2021 So, there has been an issue where the Pace framework has been corrupting the memory space of other plugins, causing random plugins to crash when they are first loaded. There is a workaround for this - check out the following threads, and see if they help. (I'm not saying this *is* your issue, but it has similar symptoms so is worth looking into) viewtopic.php?f=1&t=152787 viewtopic.php?f=1&t=151858&start=40 viewtopic.php?f=1&t=149772&p=801956#p801956 Quote Link to comment Share on other sites More sharing options...
coastcj Posted January 19, 2021 Author Share Posted January 19, 2021 < Double-click the plugged in iLok in the left-hand location column to open the Details Pane. Click the "Synchronize" link and wait until the process completes. Verify that all expected licenses are now seen on your iLok, or in some cases, a license may be in your account instead of on the iLok. All expired licenses will be moved to your account. There is also some software that has been known to interfere with USB recognition. Do you have any of the following applications installed: ~Duet or Duet Display ~USB Network Gate or any other software from Eltima ~Shadow PC >> This is from iLok support. I tried above successfully but still failed to open older sessions that were crashing. I can't confirm if it fixes future sessions yet though. I replied with error log to iLok, and I will post any status updates here. It's one reason why I keep my music computer as clear as possible to avoid things like this, and to be sure I still am not claiming iLok is my issue. Quote Link to comment Share on other sites More sharing options...
coastcj Posted January 19, 2021 Author Share Posted January 19, 2021 I also noticed another peculiarity today, in that once I get the session open with a workaround , if I close this session and don't quit Logic, I can do almost anything, i.e. create new sessions, open other ones, etc... and then re-open an errant one successfully. However, if I quit Logic, then the session will fail on next open and I need to repeat workaround again. Quote Link to comment Share on other sites More sharing options...
des99 Posted January 19, 2021 Share Posted January 19, 2021 Yes, this is essentially the previously posted workaround in action. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.