brennenfromfarmington

Q: Macbook Pro Retina with Yosemite keeps crashing while using Logic X

My laptop keeps crashing when I'm using logic, usually while I'm playing back a project with 5 or more tracks. It seems to crash because it can't process all of the audio quick enough. My laptop will freeze for about 15 seconds and then restart itself. It's fairly new, so I'm not sure why it's having problems. Here are my laptop specs:

     OS X Yosemite Version 10.10.3

     Macbook Pro (Retina, 13-inch, Early 2013)

     Processor: 2.6 GHz Intel Core i5

     Memory: 8GB 1600 MHz DDR3

     Graphics: Intel HD Graphics 4000 1024 MB

 

     And here is one of the crash logs, they are the same every time:

May 25 10:12:27.137421 Brennens-MacBook-Pro.local discoveryd_helper[160]: Basic RemoteControl com.apple.discoveryd_helper Starting XPC Server

May 25 10:12:27.143728 Brennens-MacBook-Pro.local discoveryd_helper[160]: Detailed RemoteControl com.apple.discoveryd_helper XPC connection 0x7fd889c00cd0: start (pid=73, <unknown> not root)

 

I understand that Logic might not be able to handle all of the audio I'm asking it to process, but on my older macbook with garageband it would just stop playing and give me an error message when that happened, not restart my whole computer.

 

Hopefully this is in the right category

MacBook Pro with Retina display, OS X Yosemite (10.10.3)

Posted on May 25, 2015 9:29 AM

Close

Q: Macbook Pro Retina with Yosemite keeps crashing while using Logic X

  • All replies
  • Helpful answers

  • by Eric Root,

    Eric Root Eric Root May 25, 2015 10:33 AM in response to brennenfromfarmington
    Level 9 (71,593 points)
    iTunes
    May 25, 2015 10:33 AM in response to brennenfromfarmington

    Try a restart.

     

    Do a backup, using either Time Machine or a cloning program, to ensure files/data can be recovered. Two backups are better than one.

     

    Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work. The intent is to see if it is specific to one account or a system wide problem. This account can be deleted later.

     

    Isolating an issue by using another user account

     

    If the problem is still there, try booting into the Safe Mode using your normal account.  Disconnect all peripherals except those needed for the test. Shut down the computer and then power it back up after waiting 10 seconds. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear. The boot up is significantly slower than normal. This will reset some caches, forces a directory check, and disables all startup and login items, among other things. When you reboot normally, the initial reboot may be slower than normal. If the system operates normally, there may be 3rd party applications which are causing a problem. Try deleting/disabling the third party applications after a restart by using the application un-installer. For each disable/delete, you will need to restart if you don't do them all at once.

     

    Safe Mode - About

     

     

    Safe Mode - Yosemite

  • by Linc Davis,

    Linc Davis Linc Davis May 25, 2015 10:41 AM in response to brennenfromfarmington
    Level 10 (207,990 points)
    Applications
    May 25, 2015 10:41 AM in response to brennenfromfarmington

    These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.

    Launch the Console application in any of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad and start typing the name.

    Step 1

    For this step, the title of the Console window should be All Messages. If it isn't, select

              SYSTEM LOG QUERIES All Messages

    from the log list on the left. If you don't see that list, select

              View Show Log List

    from the menu bar at the top of the screen.

    In the top right corner of the Console window, there's a search box labeled Filter. Enter "BOOT_TIME" (without the quotes.)

    Each message in the log begins with the date and time when it was entered. Select the BOOT_TIME log message that corresponds to the last boot time when you had the problem. Now clear the search box to reveal all messages. Select the ones logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

    For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.

    If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.

    When posting a log extract, be selective. A few dozen lines are almost always more than enough.

    Some private information, such as your name, may appear in the log. Anonymize before posting.

    Please don't indiscriminately dump thousands of lines from the log into this discussion.

    Please don't post screenshots of log messages—post the text.

    Step 2

    In the Console window, select

              DIAGNOSTIC AND USAGE INFORMATION System Diagnostic Reports

    (not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select

              View Show Log List

    from the menu bar.

    There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.

    I know the report is long, maybe several hundred lines. Please post all of it anyway.

    If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

    In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

    Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

    When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

  • by brennenfromfarmington,

    brennenfromfarmington brennenfromfarmington May 25, 2015 10:50 AM in response to Linc Davis
    Level 1 (0 points)
    May 25, 2015 10:50 AM in response to Linc Davis

    I already posted the logs, please don't just post spam without reading the original post.

  • by Linc Davis,

    Linc Davis Linc Davis May 25, 2015 10:58 AM in response to brennenfromfarmington
    Level 10 (207,990 points)
    Applications
    May 25, 2015 10:58 AM in response to brennenfromfarmington

    You didn't post the information I asked for, but it doesn't matter, because I'm done with this discussion and with you.

  • by brennenfromfarmington,

    brennenfromfarmington brennenfromfarmington May 25, 2015 11:02 AM in response to brennenfromfarmington
    Level 1 (0 points)
    May 25, 2015 11:02 AM in response to brennenfromfarmington

    So I opened the activity monitor and then ran logic with 4 times the amount of tracks I usually have, while also having safari and iTunes open, and the processor was barely reaching 25%, so that's not the problem. The memory is also staying below 5 out of 8 GB. Screen Shot 2015-05-25 at 11.58.42 AM.png

    I created another admin user and it worked fine, but it's also working fine in my normal user account right now, so I'm not really sure why it crashes sometimes and not other times.

  • by JimmyCMPIT,

    JimmyCMPIT JimmyCMPIT May 25, 2015 11:08 AM in response to brennenfromfarmington
    Level 5 (7,607 points)
    Mac OS X
    May 25, 2015 11:08 AM in response to brennenfromfarmington

    10.1.1 had bug fixes if you have not updated already.

    Logic Pro X 10.1.1 Release Notes - Apple Support

    but it could be the limits of your box.