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

Oct 4, 2017 12:28 PM in response to AlexGzz

Hi AlexGzz


The command jettison should be part of the second line of code, i.e:

/usr/sbin/BootCacheControl jettison

- with no line breaks


If this doesn't work, it seems like you have a similar issue to my own. If you start up in Single User mode and then continue to boot by entering exit <and pressing enter>, could you advise what the last lines of code are?

Dec 6, 2017 11:32 AM in response to Zcomuto

Hi everyone,


I’ve been following this discussion because this problem happened to me too, just yesterday. I own a MacBook Pro 13 inches Early 2011 and unfortunately I have no Time Machine Backup.


- I tried reinstalling High Sierra but it didn’t work.

- I tried with the nano CommandCache modification but it didn’t worked neither.

- I tried to fix it from the Command+S mode with the fsck codes, but is still stocked.

- Command+Option+P+R makes no difference.

- Fix HD from Disk Utility was useless too.


Here is an idea, but I would appreciate your advices before I do this, my info and my work is highly compromised.


1. Make a partition of the HD and use the Clean part for the process.

2. Re install MacOS High Sierra in the clean part (I don’t know if that’s possible)

3. If the second step works I will be able to Open my desktop but my data will be hold in the “dirty” part of the HD

4. Using Disk Utility App, plug in an external Hard Drive and use the option Restore. This will give the option to restored it from a different image (in this case, the dirty part of the HD) copy all items there.

5. Open the External Hard Drive in another computer and take the essential info out of it. Format the External Hard Drive and them copy the info back, to paste it in the clean version of the HD.


Thanks! And BTW it’s really bad to read this is happening to so many users.


Apple do something about it!

Jan 31, 2018 3:05 PM in response to Zcomuto

Had the same issue. Tried everything, even reinstalling the OS again (not deleting data) and it didn't help. I solved it by installing the os on an external HD through the recovery of mac (cmd+r on startup), booting my mac from that external HD, retrieving my data (with Migration Assistant), then deleting my internal HD, reinstalling the OS there, and migrating again from the external HD to the internal HD. Took me endless hours because the drives aren't SSD, but I finally managed to boot to my mac without being stuck after the login with almost no data loss. Hope that helps.

May 15, 2018 7:56 AM in response to vipingupta

Suggesting, your defective startup volume is named "Macintosh HD" one have to be very sensible with blanks in the command line.


After "cd" a blank is needed and after "Macintosh\", too. so the correct command would be:


cd /Volumes/Macintosh\ HD/var/db/caches/opendirectory/


The first blank splits the command "cd" from its parameters (the target directory).

The backslash "\" tells the command line that the following blank belongs to the string "Macintosh" and is NOT a delimiter for a parameter or something.


Be careful. Using wrong commands or parameters can be very dangerous in Terminal.


Much luck!

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.