burtonac Posted January 10, 2018 Share Posted January 10, 2018 I have been using Logic Pro X for years. My Mac OS is updated. I have the latest release of Logic Pro X, no update needed. When I first tried to launch it today (it's been maybe 2 months), the icon bounced for a bit. It started to do a system check, including checking Native Instruments plugins. It was an unusual start, it seems. Then it stopped. I got an error message: "Logic Pro X quit unexpectedly." I tried reopening it, and it went straight to "Logic Pro X quit unexpectedly." I tried rebooting. No luck. I looked for solutions online. I was able to SUCCESSFULLY launch Logic Pro X while holding down "Control" and then hitting "Don't Launch" when the dialogue popped up "Do you want to launch the “Core Audio” driver?" But if I open that way, nothing works--I can't create an audio track, can't change audio I/Os, can't launch Plugin Manager, nothing. Anyone have advice on what is going on? THANK YOU! Quote Link to comment Share on other sites More sharing options...
Eric Cardenas Posted January 10, 2018 Share Posted January 10, 2018 Sounds like it could be related to a 3rd party plug-in. First thing I would do is to start Native Access and make sure that your Native plug-ins are up to date. If this isn't the issue you can try this method: Go to /Library/Audio/Plug-Ins , and create a new folder called 'Disabled Components' Move half of your plug-ins inside the Components folder to the new Disabled Components folder. Launch Logic and see if that works. If it doesn't swap the contents of those folders and hope for the best. Keep adding plug-ins to the Components folder until you find the culprit. (using this 1/2 of 1/2 of 1/2.. method should speed things up. Hope that helps. /E Quote Link to comment Share on other sites More sharing options...
maceasy Posted January 10, 2018 Share Posted January 10, 2018 If you look at the log when it crashes you may well find the plugin which is the culprit. Quote Link to comment Share on other sites More sharing options...
burtonac Posted January 10, 2018 Author Share Posted January 10, 2018 Much appreciated--I will give this a shot! Quick follow-up--I was unable to find "/Library/Audio/Plug-Ins"--the only "Library" folders are in the Native Instruments director (or other unrelated applications). Any ideas on where I can find that? Quote Link to comment Share on other sites More sharing options...
Eric Cardenas Posted January 10, 2018 Share Posted January 10, 2018 In Finder choose Go > Go To Folder, from the Menu bar. Type: /Library/Audio/Plug-Ins Quote Link to comment Share on other sites More sharing options...
burtonac Posted January 10, 2018 Author Share Posted January 10, 2018 Awesome, thanks (not sure why it wasn't showing up in search results!) Quote Link to comment Share on other sites More sharing options...
Solution burtonac Posted January 10, 2018 Author Solution Share Posted January 10, 2018 Problem solved! Turns out my Logic Pro X was 6 versions old. For some reason, the App Store was not showing that I needed to upgrade. I had to trash and reinstall the Logic Pro X app entirely, which (fortunately) had no impact at all on my projects it appears. Hope this is helpful to the community here! Eric, many thanks for your help--I will keep these tips in my back pocket in case I encounter future issues! Quote Link to comment Share on other sites More sharing options...
Eric Cardenas Posted January 10, 2018 Share Posted January 10, 2018 You're most welcome! I'm glad that it was just an update issue. Quote Link to comment Share on other sites More sharing options...
sourcefor Posted June 18, 2021 Share Posted June 18, 2021 Yeah My Logic Pro 10.6.2 is acting up again! I've removed ALL plugins, Tried to start without CORE AUDIO activated and it just crashes immediately without opening! Tried to open a blank session and it opens, when I try to open the old session from the import function it crashes! Everything is updated, OS Catalina, Native Instruments, etc. It never tells me the reason it crashed either! what gives? Thanks! Quote Link to comment Share on other sites More sharing options...
triplets Posted June 18, 2021 Share Posted June 18, 2021 I would remove all plugins from the Components folder and try to launch Logic again. Quote Link to comment Share on other sites More sharing options...
sourcefor Posted June 18, 2021 Share Posted June 18, 2021 Does the following show anything: Process: Logic Pro X [2775] Path: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X Identifier: Logic Pro X Version: 10.6.2 (5437) Build Info: MALogic-5437000000000000~2 (10U141) App Item ID: 634148309 App External ID: 841256562 Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Logic Pro X [2775] User ID: 502 Date/Time: 2021-06-18 18:48:56.352 -0400 OS Version: Mac OS X 10.15.7 (19H1217) Report Version: 12 Bridge OS Version: 5.4 (18P4663) Anonymous UUID: 01B18802-C51B-4E6C-833C-3B90EE9DC454 Time Awake Since Boot: 1500 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Application Specific Information: Dublin | 6b34edbe1e2428234532a9a90f0dda622834cd344de3e01f645f6cf5be04bce1 | 781cc937bdf8fcedde9f5ae075d75e80eb832333 | 2021-04-20_07:21:15 terminating with uncaught exception of type std::out_of_range: vector abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff6efa133a __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff6f05de60 pthread_kill + 430 2 libsystem_c.dylib 0x00007fff6ef28808 abort + 120 3 libc++abi.dylib 0x00007fff6c187458 abort_message + 231 4 libc++abi.dylib 0x00007fff6c1788a7 demangling_terminate_handler() + 238 5 libobjc.A.dylib 0x00007fff6dcb35b1 _objc_terminate() + 104 6 libc++abi.dylib 0x00007fff6c186887 std::__terminate(void (*)()) + 8 7 libc++abi.dylib 0x00007fff6c186829 std::terminate() + 41 8 libdispatch.dylib 0x00007fff6ee0066c _dispatch_client_callout + 28 9 libdispatch.dylib 0x00007fff6ee0bcab _dispatch_main_queue_callback_4CF + 936 10 com.apple.CoreFoundation 0x00007fff34ddb911 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9 11 com.apple.CoreFoundation 0x00007fff34d9b717 __CFRunLoopRun + 2028 12 com.apple.CoreFoundation 0x00007fff34d9a8ce CFRunLoopRunSpecific + 462 13 com.apple.HIToolbox 0x00007fff339c6abd RunCurrentEventLoopInMode + 292 14 com.apple.HIToolbox 0x00007fff339c66f4 ReceiveNextEventCommon + 359 15 com.apple.HIToolbox 0x00007fff339c6579 _BlockUntilNextEventMatchingListInModeWithFilter + 64 16 com.apple.AppKit 0x00007fff3200d039 _DPSNextEvent + 883 17 com.apple.AppKit 0x00007fff3200b880 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1352 18 com.apple.logic10 0x0000000101dea630 0x1003e1000 + 27301424 19 com.apple.AppKit 0x00007fff31ffd58e -[NSApplication run] + 658 20 com.apple.AppKit 0x00007fff31fcf396 NSApplicationMain + 777 21 com.apple.logic10 0x0000000100f90b5d 0x1003e1000 + 12254045 22 libdyld.dylib 0x00007fff6ee59cc9 start + 1 Thread 1: 0 libsystem_pthread.dylib 0x00007fff6f059b68 start_wqthread + 0 Thread 2: 0 libsystem_pthread.dylib 0x00007fff6f059b68 start_wqthread + 0 Thread 3:: JavaScriptCore bmalloc scavenger 0 libsystem_kernel.dylib 0x00007fff6ef9d882 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fff6f05e425 _pthread_cond_wait + 698 2 libc++.1.dylib 0x00007fff6c12c592 std::__1::condition_variable::wait(std::__1::unique_lock&) + 18 3 com.apple.JavaScriptCore 0x00007fff3959a274 void std::__1::condition_variable_any::wait >(std::__1::unique_lock&) + 84 4 com.apple.JavaScriptCore 0x00007fff3959ea7b bmalloc::Scavenger::threadRunLoop() + 299 5 com.apple.JavaScriptCore 0x00007fff3959e649 bmalloc::Scavenger::threadEntryPoint(bmalloc::Scavenger*) + 9 6 com.apple.JavaScriptCore 0x00007fff395a0d27 void* std::__1::__thread_proxy >, void (*)(bmalloc::Scavenger*), bmalloc::Scavenger*> >(void*) + 39 7 libsystem_pthread.dylib 0x00007fff6f05e109 _pthread_start + 148 8 libsystem_pthread.dylib 0x00007fff6f059b8b thread_start + 15 Quote Link to comment Share on other sites More sharing options...
sourcefor Posted June 19, 2021 Share Posted June 19, 2021 and Why can't I open up at least 5 recent sessions that I worked on this past week, They cannot all be corrupted and I can open up template with all of my plugins instantiated! 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.