crashed: too many corpses being created

After installing a Yosemite update on my laptop, when it boots, it seems to all be fine until about the loading bar is maybe 2/3 done, then slows to a crawl and takes another 20 minutes or so to reach full - where it stays. I have no cursor or anything else during this time, but my caps lock button light will go on an off when I press it.

I've tried:
-Resetting PRAM/NVRAM
-Booting into recovery mode and repairing the drive/partition. This seemed to be done successfully.
-Booting hardware diagnostics and doing a check. It says everything is fine.
-Safe boot. Takes the same length of time and hangs at the same place, so honestly not sure if I'm even doing it right.
-Verbose mode says every single process has crashed, with 'too many corpses being created.'. (picture - note that it's not actually blurry, just scrolling pretty fast so a photo wasn't the best)

It's a Mid-2011 15" Macbook pro, 2.2GHz with a 750GB hard drive and 16GB of RAM. I'm still doing a few other checks (currently re-installing 10.10 using a thumb drive to see if that fixes it), but has anyone got any ideas or had a similar problem?

MacBook Pro (15-inch Early 2011), OS X Yosemite (10.10.3)

Posted on Jun 27, 2015 2:24 PM

Reply
Question marked as Top-ranking reply

Posted on Oct 1, 2017 4:49 AM

The following didn't work for me, but creating/fixing the file rc.server has worked for many others with a similar problem. To do this, boot up your Mac in Single User mode (hold Cmd+S immediately as you hear the Apple chime).


Once the initial verbose script has finished loading, enter the following two lines:

mount -uw /

/usr/bin/nano /etc/rc.server

The first line allows your Mac's system files to be written to. The second line opens/creates rc.server as a file, using the nano process. Once the file opens, delete any script that already exists (don't worry if it's empty) and then enter the following two lines:

#!/bin/sh

/usr/sbin/BootCacheControl jettison

Once finished, save your changes with Ctrl+O and then exit nano with Ctrl+X. Your Mac may then automatically reboot, but if it returns you to Single User mode, enter the following line:

reboot


Credit to Chris Hotte (a.k.a NightFlight) for originally discovering this fix


Hope this works for you!


Note: if you're using a UK-type keyboard like myself, you might have a hard time creating the # hash symbol required for the rc.server script. UK input requires Alt+3 to create #, but Alt seems to have no effect within Single User mode. To get around this, I used Recovery Mode (boot up and hold Cmd+R) and changed my input to a US keyboard, then rebooted. US input uses Shift+3 to get #, which works fine in Single User mode

76 replies

Jan 4, 2018 9:44 AM in response to ciamine

This path is under OS Yosemite. I have had the problem about one month ago, when I posted for the first time here, under OS High Sierra. The symptoms are the same everywhere, you do it right, I think, it is not solvable in my opinion. You will have to recover via Time Machine as I did. It's a shame on Apple.

By the way I wish to point out that I normally am a safe user, that means I make a backup before updating the OS to a new one (and after) with Time Machine. But the problem is particularly insidious because, at least in my case, it let 15 days pass without issues, and then (I believe after the infamous obligatory safety update) it struck! So I lost 15 days because I just connect my external Time Machine disk every ... you have guessed, 15 days! (this is a typical Murphy's law effect: it struck the day before my planned Time Machine backup). 👿

Regards

Claudio

Jan 15, 2018 1:52 PM in response to The Sticky bandit

Sticky bandit, this is very similar to my solution, I described here:


Boot failure after High Sierra Update


I simply migrated everything from the faulty volume, for the OS itself wont't be migrated and therefore the "too many corpses being created" error stayed away. We really got everything back. Hooray!


Good luck to everyone with the same problem!


Greetings from Hamburg

Jan 3, 2018 5:14 PM in response to Zcomuto

So I had the same issue. Tried everything in the book while booting it up in verbose mode. Eventually, while trying to Reset PRAM, change boot options, reinstalling MacOS, etc, the command line in verbose mode said something along the lines of “ran out of...” at around 200 or so logs of “too many corpses created” and after that it started up like normal. Hope this helps

Sep 30, 2017 1:30 AM in response to Zcomuto

So, I’m having the exact same issue on my recent install of High Sierra.


Having attempted to reinstall OS X multiple times, I’m almost at the limit of my patience. Even more frustrating is that I made a small partition on my HD and ran a clean install of High Sierra there, which works perfectly.


What Zcomuto was probably referring to is “OSInstallerScripts” - this is/was an option

that OS X’s installer app used to offer in a customisable install. It is used to install or repair the boot script that required for a Mac after a new install of OS X. Only problem is that OS X installer doesn’t seem to offer a custom install option anymore, so you can’t specifically choose to do this anymore (except for the developer beta installer, which is customisable, according to info found on Google)


I found this out by starting up my broken install in single-user verbose mode and tracking the script. I got an infinite amount of lines telling me each individual process had “crashed” with “too many corpses being created”. I had (and still have) no idea what this means, but found online that people installing older versions of OS X (and Hackintoshes, by the way) were able to fix the same problem, by running a custom install and selecting OSInstallScripts only, without reinstalling the whole OS


I’m posting this so people with the same issue today might know what they’re dealing with, and in the faint hope that anyone reading knows how to isolate OSInstallerScripts, to run for an install of High Sierra.

Dec 2, 2017 6:04 AM in response to Zcomuto

Hi everyone


after installing High Sierra I think I’m experiencing the same. My iMac reaches only the end of the progress bar under the Apple logo and then hangs there indefinitely. In the verbose mode safe start I get all these messages “too many corpses being created”.


Can someone please provide a simple explanation what’s going on and how to solve the problem?


thanks a lot in advance

best regards

Claudio

Dec 18, 2017 1:01 PM in response to Anfrabegom14

Hi

same problem with my IMac with high sierra.

I called Apple Assistance and talked about DSMOS and “too many corpses being created”.

they asked me to follow all rebooting steps already done but it was useless.

I tried this topic and I’am still waiting for my computer to end rebooting...

It is a shame for Apple not to cope with this problem seriously.

I have yet to try restoration from time machine.

Jan 4, 2018 7:41 AM in response to Zcomuto

same problem

I've tried:

-Resetting PRAM/NVRAM

-Booting into recovery mode and repairing the drive/partition. This seemed to be done successfully.

-Booting hardware diagnostics and doing a check. It says everything is fine.

-Safe boot. Takes the same length of time and hangs at the same place, so honestly not sure if I'm even doing it right.

-Verbose mode says every single process has crashed, with 'too many corpses being created.

nothing happened....

Do you resolve this problem?

Jan 14, 2018 3:26 AM in response to The Sticky bandit

Thank you, this helped me so much. I tried everything for an entire day and finally, I got my photos and documents back!


I have a question though: “I then wiped and restored my old hard drive with my external hard drive. Basically returning my hard drive back to how it was before the dreaded "too many corpses being created" Boom, and thats how I saved my files with no back up.”


How did you wipe the old drive and did you not install the same version of iOS that gave you the problems in the first place?

Feb 5, 2018 3:15 PM in response to Zcomuto

I have the same problem with the new osx high sierra update installed. i took it to apple and they reinstalled the operating system and now that i got home its still freezing at the loading bar. any idea what i could do since reinstalling the operating system isn't fixing it? should i try installing a older mac operating system maybe

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

crashed: too many corpses being created

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.