1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

LOGIC PRO X - Frequent crashes with this error...

Discussion in 'Logic Pro X' started by PIANO_DAN, Jan 12, 2015.


    PIANO_DAN New Member

    I'm fairly new to Apple and Logic Pro X. I'm making backing tracks for a show, however a couple of files are causing LOGIC to crash. It seems to be at a certain point in the track. They are all software instruments and kontakt player rather than Audio files.

    I have no idea what the error report means, which I've pasted some of below. I hope someone can help decipher what it could be.

    I'm running Pro X 10.0.7 on:

    Model Name: MacBook Pro
    Model Identifier: MacBookPro9,2
    Processor Name: Intel Core i7
    Processor Speed: 2.9 GHz
    Number of Processors: 1
    Total Number of Cores: 2
    L2 Cache (per Core): 256 KB
    L3 Cache: 4 MB
    Memory: 8 GB


    Process: Logic Pro X [608]
    Path: /Users/USER/Desktop/Logic Pro X.app/Contents/MacOS/Logic Pro X
    Identifier: com.apple.logic10
    Version: 10.0.7 (3166.30)
    Build Info: MALogic-3166030000000000~1
    App Item ID: 634148309
    App External ID: 337342644
    Code Type: X86-64 (Native)
    Parent Process: ??? [1]
    Responsible: Logic Pro X [608]
    User ID: 501

    Date/Time: 2015-01-10 19:02:45.404 +0000
    OS Version: Mac OS X 10.10.1 (14B25)
    Report Version: 11
    Anonymous UUID: 24D0BB52-A877-81DA-C718-FA2288337570

    Sleep/Wake UUID: 60BCBDC1-6BDE-4AEA-9E8E-2A185E8DE15B

    Time Awake Since Boot: 1300 seconds
    Time Since Wake: 570 seconds

    Crashed Thread: 8 SeqTimer

    Exception Type: EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x000000010e4f9000

    Thanks in anticipation!
  3. gdoubleyou

    gdoubleyou Senior member

    Try repairing permissions with the Disk Utility.

    To free up your CPU, bounce or freeze the virtual instruments.


    PIANO_DAN New Member

    Thanks for your suggestion. By trial and error, I found that the culprit was a "redundant orphan" track or something, from recording two tracks at same time.

Share This Page