Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MP 7,1 Mac Pro just died. Ran out of application memory then shutdown. Can’t boot. Help

machenryr

machenryr

macrumors 6502a
Original poster
Jan 25, 2016
813
192
So hopefully it’s not as tragic as this. I had a strange force quit error message. I’d been working with FCPX. I’d seen this before a few years ago. It says I’m out of application memory. Something like 293 GB. I have 192 I think. I can’t check because my MP won’t boot. I got the force quit message and I tried to quit applications including FCPX but it was frozen. So I had ignored it for a minute hoping it would regain itself when it just shutdown. I haven’t been able to get it to boot.

First I haven’t no idea why FCPX would demand that much memory. I have been fantastic but I’ve been aware of offloading projects to other drives and archiving because it does take a lot of DRIVE space. But ram??

Anyway can anyone help me rebooting here. I have an old DW copy. Not sure if it’s compatible. I’m on Monterey. Maybe someone can help reassure me that j haven’t bricked my 7,1 Mac Pro.
 
Does pressing the power button do anything? Does it try to boot? Where does it get stuck?
 
Last edited:
JesterJJZ said:
Does pressing the power button do anything? Does it try to boot? Where does it get stuck?
Click to expand...

It does nothing. No sound. Nothing on the monitor. I’ve turned off the power. Tomorrow morning if it still doesn’t boot I’ll unplug all peripherals plugged into it. Sometimes there’s a stuck USB device.
 
Last edited by a moderator:
I'd be tempted to plug and power cycle every usb and thunderbolt device on your system.

Bad USB devices can bring down the system, you don't leave them in-situ. I've had a partially unplugged USB cable crash my system, also a bugged US hub in a display, that required the display to be power cycled.
 
  • Like
Reactions: izzy0242mr
disconnect all peripherals, disconnect the mac from power for 15 secs, reconnect power, press and hold the power button for ”3 mississippi’s”. release the power button and (having connected a wired keyboard) reset nvram.
If nothing happens open the side and check wether any LED inside is light up (and its color). report here.
 
  • Like
Reactions: throAU
Slartibart said:
If nothing happens open the side and check wether any LED inside is light up (and its color). report here.
Click to expand...
You can not open the side, as was possible on the old Mac Pros. The rack Mac Pro 2019 can open a hatch to let one look inside while it is running.

machenryr said:
What is that??
Click to expand...
I have no idea either. Never saw a post om macrumors that looked like that :oops:

When you try to boot it. Does the led light turn on, next to the start bottom? I know it can display a flashing SOS if something is really wrong
 
Regulus67 said:
You can not open the side, as was possible on the old Mac Pros. The rack Mac Pro 2019 can open a hatch to let one look inside while it is running.
Click to expand...
yes, my bad. for whatever reason I thought of the wrong MPro model.
 
I recommend starting with the basics. @Slartibart mentioned some of them. I would take it a step further and recommend removing all but what is necessary to power on the system. Remove all memory except the bare minimum necessary, then swap modules if the problem persists. Remove all storage except the boot drive. Same for any internal cards.

I suspect the hardware caused your application memory issue and that the application memory issue did not do anything to the system.

​

 
Thank you everyone! I turned the power off over night. It came back on with a report. Thank goodness! Now my question is why does FCPX have such a profound memory leak? Is there an update I didn’t get? First time I encountered this was two years ago.
 
Last edited by a moderator:
Ok. There is a bug here that keeps scrambling my posts. I wanted to thank everyone. It worked. Turned the power completely off in the studio over night. It essentially was like unplugging all peripherals. Now I just need to find out why there is this leak in FCPX. First time I saw this was two years ago. I thought it was fixed in an update. Maybe I didn’t get it? Let’s see if this posts correctly.
 
I think I have it but I’ve never used it. FCPX works for me. I don’t want to relearn anything at this point. Not a fan of learning curves. What does it do that FCPX doesn’t that’s worth the hassle? Now I keep my eyes on the activity monitor and quit it once in awhile. I was doing several projects one after the other. It probably never dumps its cache between them.
 
Last edited by a moderator:
machenryr said:
What does it do that FCPX doesn’t that’s worth the hassle?
Click to expand...

Runs on Linux & Windows so that when Apple's pro hardware range is inevitably shuttered, and FCP goes subscription-priced, before being cancelled entirely, you can choose a different hardware vendor.

At least until Apple tries to buy Blackmagic, because they haven't been capable of writing a significant piece of application software in over a decade.
 
  • Like
Reactions: ddhhddhh2
Delete your preferences - To delete preferences, hold down command and option while starting FCP X and click Delete Preferences - Reopen your library.

Also check Activity Monitor and find out when it’s starts grabbing all your memory - it maybe that your FCPX is corrupted - you also might trying First Aid on your HardDrive - BTW do you have a SSD or Fusion Drive?
 
Papanate said:
... BTW do you have a SSD or Fusion Drive?
Click to expand...
A Mac Pro 2019 does not have Fusion Drive or a SATA SSD.
You can have from 256GB - up to 8TB SSD

Screenshot 2025-02-10 at 17.50.21.png
Screenshot 2025-02-10 at 17.49.16.png


apple ssd kit.jpg
 
  • Like
Reactions: MarkC426
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back