Logic Pro Crashes – Make The Most Of Them

mac crash

Let’s talk crashes. I must say I’ve had my dose through the years. I tend to update Logic Pro rather quickly after there’s an update out, which isn’t always the smartest thing to do. I run a pretty big collection of third-party plugins – so I easily lose track of version updates. Dealing with crashes unfortunately is an integral part of working with Logic Pro, so let’s have a look at what you can do to find out more about the cause of a crash.

These are the steps I follow whenever I get this warm welcome:

After clicking ‘quit’, if all goes well, this pops up:

After clicking ‘Report’. This dialogue appears:

I never leave a comment. Given the state I’m in after a crash, chances are it won’t begin with ‘Dear Steve’ anyway, so I just leave it empty. Before you send it to Apple (you should), hit ‘Show Details’.

If you’re not getting any of these dialogues after the crash, you can find the crash report in


Doubleclick the most recent report, and it will open in the Console application (located in Applications/Utilities).

Finding The Culprit

After either clicking ‘Show Details’ or opening the crash report in Console, look up the thread that crashed:

  • Thread 0 Crashed: Dispatch queue: com.apple.main-thread
  • 0 libSystem.B.dylib 0x973c2156 __kill + 10
  • 1 libSystem.B.dylib 0x973c2148 kill$UNIX2003 + 32
  • 2 libSystem.B.dylib 0x97454899 raise + 26
  • 3 libSystem.B.dylib 0x9746a94d __abort + 124
  • 4 libSystem.B.dylib 0x9746a9c9 abort_report_np + 0
  • 5 com.apple.logic.pro 0x00408209 std::ostream& TraceOutContainer(std::ostream&, CEvs, char const*, int) + 3981977
  • 6 libSystem.B.dylib 0x973c745b _sigtramp + 43
  • 7 ??? 0x0000000a 0 + 10
  • 8 com.apple.prokit 0x010cdc59 -[NSProSegmentedScrubberCell trackMouse:inRect:ofView:untilMouseUp:] + 285
  • 9 com.apple.prokit 0x010c5575 -[NSProSegmentedScrubber mouseDown:] + 218
  • 10 com.apple.AppKit 0x95760c68 -[NSWindow sendEvent:] + 5549
  • 11 com.apple.prokit 0x0100e7c0 -[NSProPanel sendEvent:] + 264
  • 12 com.apple.logic.pro 0x007e7353 std::ostream& TraceOutContainer(std::ostream&, CEvs, char const*, int) + 8041443
  • 13 com.apple.logic.pro 0x0003f886 std::ostream& TraceOutContainer(std::ostream&, CEvs, char const*, int) + 14614
  • 14 com.apple.AppKit 0x95679817 -[NSApplication sendEvent:] + 6431
  • 15 com.apple.prokit 0x00fedbb0 -[NSProApplication sendEvent:] + 1901
  • 16 com.apple.logic.pro 0x006349dd std::ostream& TraceOutContainer(std::ostream&, CEvs, char const*, int) + 6261357
  • 17 com.apple.logic.pro 0x006391be std::ostream& TraceOutContainer(std::ostream&, CEvs, char const*, int) + 6279758
  • 18 com.apple.logic.pro 0x00634a0f std::ostream& TraceOutContainer(std::ostream&, CEvs, char const*, int) + 6261407
  • 19 com.apple.AppKit 0x9560d2a7 -[NSApplication run] + 917
  • 20 com.apple.prokit 0x00fedf5c NSProApplicationMain + 326
  • 21 com.apple.logic.pro 0x0002b7b5 DummyConnection::DummyConnection() + 193
  • As you can see, thread 0 crashed. This list is in reverse chronological order, so the last task right before the crash is at the top. The system component is on the left (libSystem.B.dylib) and the task is on the right. Having entered geek territory, we need help, so let’s visit a forum.

    Site Specific Google Search

    Before I jump to my favorite forum, I always use Google first. I use a site specific search:
    ‘site:(domain to be searched) (searchterm)’.

    In this case, a good query would be “site:logicprohelp.com libSystem.B.dylib”.

    A good idea here is to narrow down the search by adding a version number (9.1.3 in my case) to the search query, and move from there. This typical crash, I learned, turns out to be almost perfectly replicable on 9.1.3 running on OSX 10.6.7. Read about it here. I bumped into a bug.

    The Audio Unit Crash

    When a third party Audio Unit is the culprit, often more specific action can be taken. One day I was editing vocals in Melodyne, when Logic suddenly crashed. I checked logs, and found a suspect, its name ending with “.music.apps.MAAudioEngine”. Searching that pointed to Melodyne. Basically I was left with two choices: update the plugin, and if that didn’t work, disable the plugin in the Audio Units Manager. But what if a plugin causes a crash right after loading your project, and you’ve set that project as the default song?

    Logic Pro Startup Modes

    By using modifier keys while you open the application, you can put Logic Pro or into one of several troubleshooting modes. Just go to your Applications folder, double-click the Logic icon, and then immediately hold down the respective modifier key(s) until Logic Pro is fully loaded.

    • Launch Logic Pro, then hold down [option]
    • This will open Logic Pro without Autoload/Template/LastRecent.

    • Launch Logic Pro, then hold down [ctrl]
    • This will open Logic Pro without the audio engine.

    • Launch Logic Pro, then hold down [ctrl] and [shift]
    • AU-Safe Mode. This will skip plugins that didn’t pass validation.

    I know, having to stop right in the middle of your creative flow can be very frustrating, if not unhealthy. But at least now you know some ways to be back on your feet when Logic Pro crashes again, either with or without the faulty plugin. And if it turns out to be a bug, always report the crash to Apple, or submit the report to your favorite help forum.

    Related Posts:

    Follow Logic Pro Expert