Logic Pro X Crashes When Shutting Down

Question

Logic Pro X Crashes When Shutting Down

I previously had a late 2016 iMac with 32g ram, intel quad core processor. Logic would almost consistently crash when I was shutting it down. It would appear to shut down correctly, and then sometimes up to a minute or more later it would say "Logic Pro X Quit Unexpectedly" and give an error report. I am not computer savvy enough to understand anything in the error report. This happened most frequently on my larger projects, which typically had about 100 tracks or more, and 3rd party plugins (EZ Drummer, Izotope, Melodyne) Thinking the computer was just too old, I got a Mac mini with the M2, 12 core CPU, and 32g unified memory. Initially, with the new computer Logic started crashing even more as I was reenabling (1 by 1), my 3rd party plugins. Then I began running Logic in Rosetta, which appeared to help with random crashes while the project was open, but when I shut down Logic, it is crashing, just like before.

I am wondering if even my new Mac mini is not enough to run my larger projects, or if there is anything else I can do to stop Logic from crashing.

Any help would be GREATLY appreciated. Below is the beginning of the error report I am receiving when it crashes upon shutdown.

-------------------------------------

Translated Report (Full Report Below)

-------------------------------------

Process: Logic Pro X [2532]

Path: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X

Identifier: com.apple.logic10

Version: 10.7.9 (5830)

Build Info: MALogic-5830000000000000~3 (1A73)

App Item ID: 634148309

App External ID: 857501258

Code Type: X86-64 (Translated)

Parent Process: launchd [1]

User ID: 501

Date/Time: 2023-09-10 21:12:35.7111 -0700

OS Version: macOS 13.5.2 (22G91)

Report Version: 12

Anonymous UUID: D343AAEF-D4AF-DE2E-E226-01B659199AD0

Time Awake Since Boot: 12000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6

Terminating Process: Logic Pro X [2532]

Application Specific Information:

abort() called

Kernel Triage:

VM - (arg = 0x0) pmap_enter retried due to resource shortage

iMac 27″, macOS 12.6

Posted on Sep 10, 2023 09:46 PM

Reply

Answer 1

sean_67

Level 1

5 points

Jul 14, 2024 05:13 PM in response to Pullingmyhairout123

I have the same issue: Logic works fine but whenever I quit, I get the error:

“Logic Pro quit unexpectedly”. The only reason I mind is that I’m worried it might indicate instability wit Logic in the future.

Error report is included in the post. If anyone is adept at reading these and can provide some insight, I too would greatly appreciate it. I could only begin the error message because it's too long to paste in the additional text. I can provide more of it if it helps.

Mac mini 2018

3.2 GHz 6-Core Intel Core i7

16 GB 2667 MHz DDR4

Sonoma 14.5 (23F79)

"Logic Pro quit unexpectedly" after quitting Logic

Reply

Answer 2

yoyoBen

Level 4

3,329 points

Sep 10, 2023 11:53 PM in response to Pullingmyhairout123

I'm not good at crash report reading, but we can see, Thread 0 has crashed. You can lookup Thread 0, sometimes you get some useful / readable information. BTW there is an option in the forum gui to insert code into a post...

Have you used Migration Assistant when transfering old Applications, Plugins and System-related stuff to your new computer?

Reply

Answer 3

Sep 11, 2023 12:00 AM in response to yoyoBen

Thanks. I checked the crash report that I saved and can't make heads or tails of what Thread 0 was. I'll look into inserting code into a post to see if I can get some feedback there.

I did not use Migration Assistant because my old iMac had 4TB of storage, and my new Mac mini only has 1. I bought an external SSD of 4TB to make up the difference, and that is where my logic files are being stored on my new Mac mini.

Does it seem like my new Mac mini just isn't powerful enough to handle the project, or does it seem like it is some other issue (e.g. a 3rd party plug in)?

Thanks again.

Reply

Answer 4

Sep 11, 2023 12:36 AM in response to yoyoBen

Thanks! What's the best methodology to test the plugins to see which one(s) are causing the problem?

I have begun the process of going into the plugin manager and unclicking "use" on them, and testing my projects out. I haven't been able to isolate the problem. Sometimes when I unclick a particular plugin, it shuts down normally without crashing, but when I repeat the exact same process (with the same plug ins unclicked), then it crashes again. Also, even when I unclick the "use" button, the plugin still appears and works in my projects that use that particular plug in (I understand I just can't add it to new tracks). So with those plugins still operating, it seems tough for me to isolate which plugin(s) are causing the problem.

Again, thank you very much. I really appreciate any insight you could give me.

Reply