You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Luis_Mercado Author

Level 1

46 points

Guide: How to solve Yosemite memory leaks and CPU usage

I post this hoping to help those users who, like me, are experiencing high CPU usage and massive memory leaking with OS X core services and apps, leading to slow performance and battery drain.

I've tried everything mentioned, but found the right combination of steps to follow. I've tried this with seven different Apple computers, including mine, and has worked well so far. I applied this method yesterday to give these process a 24 hour window to fail again, so far everything good.

First step: disconnect any external or secondary monitors, if any is present. The video memory allocation leak can also happen if you have a system with an integrated card, like Intel, with no external monitors attached.

Second step: Shut down your machine and enter Safe Mode (press shift once you turn on your computer again, more info below). Once you're there, fix your disk permissions.

Guide of how to access Safe Mode: OS X: What is Safe Boot, Safe Mode?

Third step: From Safe Mode turn off your machine again and reset your System Management Controller (SMC). There are different methods, depending on machine, to do this. To know what method applies to yours read the following guide.

Intel-based Macs: Resetting the System Management Controller (SMC)

Fourth step: Once your machine completes a full boot after resetting the SMC turn it off again and reset your PRAM (THIS IS THE MOST IMPORTANT STEP, BUT THE PREVIOUS ONES ARE ESSENTIAL FOR THIS ONE TO WORK). The PRAM stores small bits of data that indicate our Apple computer how to interact with the devices connected to it, including monitors and video cards. It also affects software.

To reset it you should hold the OPTION, COMMAND, P and R keys in your keyboard immediately after turning on your machine again.You'll hear the start up chime, continue pressing the keys until the machine boots and the chime starts A SECOND TIME, then release. IF YOUR YOSEMITE INSTALLATION LOCKS UP AT A BLACK SCREEN AFTER THIS, DONT PANIC! It's normal, just turn off your computer and let it boot again.

More info about PRAM: OS X Mavericks: Reset your computer’s PRAM

Voila, reconnect your external displays and enjoy your system.

Message was edited by: Luis_Mercado

MacBook Air, OS X Yosemite (10.10)

Posted on Oct 23, 2014 10:45 AM

557 replies

Nov 17, 2014 1:29 PM in response to MadMacs0

Mad Macs - I just wanna say thank you for the help you gave me in my problem with mavericks --> yosemite upgrading. nothing ended up helping the problems my computer had and in the end - a couple days ago - I wiped out everything and started brand new. so far everythings been a breeze and my computer has not "felt" more smooth since erasing everything and doing a clean installation from nothing. It gave me Yosemite, which is more or less what I wanted, without bugs, and the system seems smooth - no 300% boosts in cpu usage, Safari is quick and I can open more than 3 tabs, etc. Hope everyone finds a solution to their problems but to be honest I'm content with my computer again and life is not a daily wrestle. I can now work.

Thanks for your advice

Nov 17, 2014 2:01 PM in response to MadMacs0

I had no feedback about the bug I reported (except they asked for the code). I'll wait for Christmas.

MadMacs0

Level 5

5,227 points

Nov 17, 2014 2:05 PM in response to readytorun

Glad I could help.

MadMacs0

Level 5

5,227 points

Nov 17, 2014 2:08 PM in response to ThomasKilian

ThomasKilian wrote:

I had no feedback about the bug I reported (except they asked for the code). I'll wait for Christmas.

The only feedback you will ever get is either a request for additional information when they need it (occasionally they offer special diagnostic routines they ask users to run for specific issues) or to inform you that they believe the issue was fixed with an update and request your confirmation. The latter often comes weeks or months later.

Nov 17, 2014 4:53 PM in response to MadMacs0

Exactly. I got such kind of information in the past. Since the issue is still open it's likely not fixed. Usually I jump on the train quite early but in my age I better wait for the next to come ;-) I also have different issues (like a bug in the Swift compiler) which currently stops me from doing anything meaningful. Eventually I'll check if some of my former bug reports faded away...

Yuck9

Level 1

4 points

Nov 17, 2014 7:29 PM in response to ThomasKilian

It's not fixed. Installed the newest build today with the new updates and still have problems. Thanks to Acronis backup it's a piece of cake to restore.

Nov 17, 2014 9:41 PM in response to Yuck9

Shame! Still the same!

My MBP had the memory leak und in addition it crashed while hibernating. The CPU-usage-problem seems to be fixed due to Luis' help.

But the freezing-problem of my MBP after hibernating is still there.

ALT+CMD+Eject.

The hibernationfile is written as scheduled.

Maintenance-wakeup a few hours later - CRASH:

18.11.14 00:24:54,000 kernel[0]: AppleBCM5701Ethernet [en0]: Link down (womp disabled, proxy idle)

18.11.14 00:24:55,674 discoveryd[52]: Basic Bonjour,Warn Warning: IPv4 listener multicast send failed en0, 50

18.11.14 00:24:55,674 discoveryd[52]: Basic Bonjour,Warn Warning: IPv6 listener multicast send failed en0, 50

18.11.14 00:24:57,474 discoveryd[52]: Basic Bonjour,Warn Warning: IPv4 listener multicast send failed en0, 50

18.11.14 00:24:57,475 discoveryd[52]: Basic Bonjour,Warn Warning: IPv6 listener multicast send failed en0, 50

18.11.14 00:24:58,778 discoveryd[52]: Basic Bonjour,Warn Warning: IPv4 listener multicast send failed en0, 50

18.11.14 00:24:58,778 discoveryd[52]: Basic Bonjour,Warn Warning: IPv6 listener multicast send failed en0, 50

18.11.14 00:25:04,790 loginwindow[68]: CoreAnimation: warning, deleted thread with uncommitted CATransaction; set CA_DEBUG_TRANSACTIONS=1 in environment to log backtraces.

18.11.14 00:25:33,000 kernel[0]: hibernate_page_list_setall(preflight 0) start 0xffffff80d63d6000, 0xffffff80d6416000

18.11.14 00:25:33,000 kernel[0]: hibernate_page_list_setall time: 300 ms

18.11.14 00:25:33,000 kernel[0]: pages 1592019, wire 295365, act 591718, inact 8717, cleaned 0 spec 37, zf 34364, throt 0, compr 0, xpmapped 40000

18.11.14 00:25:33,000 kernel[0]: could discard act 156777 inact 81392 purgeable 14075 spec 409574 cleaned 0

18.11.14 00:25:33,000 kernel[0]: WARNING: hibernate_page_list_setall skipped 42123 xpmapped pages

18.11.14 00:25:33,000 kernel[0]: hibernate_page_list_setall found pageCount 930201

18.11.14 00:25:33,000 kernel[0]: IOHibernatePollerOpen, ml_get_interrupts_enabled 0

18.11.14 00:25:33,000 kernel[0]: IOHibernatePollerOpen(0)

18.11.14 00:25:33,000 kernel[0]: encryptStart 14080

18.11.14 00:25:33,000 kernel[0]: bitmap_size 0x3f5a0, previewSize 0x3ddeb0, writing 928904 pages @ 0x4314d0

18.11.14 00:25:33,000 kernel[0]: encryptEnd 8db3400

18.11.14 00:25:33,000 kernel[0]: image1Size 0x11610000, encryptStart1 0x14080, End1 0x8db3400

18.11.14 00:25:33,000 kernel[0]: encryptStart 11610000

18.11.14 00:25:33,000 kernel[0]: encryptEnd 55c50200

18.11.14 00:25:33,000 kernel[0]: PMStats: Hibernate write took 25799 ms

18.11.14 00:25:33,000 kernel[0]: all time: 25799 ms, comp bytes: 3805155328 time: 2950 ms 1229 Mb/s, crypt bytes: 1295906176 time: 2081 ms 593 Mb/s,

18.11.14 00:25:33,000 kernel[0]: image 1438978048 (33%), uncompressed 3805155328 (928993), compressed 1427544880 (37%), sum1 9681197f, sum2 3057b3c2

18.11.14 00:25:33,000 kernel[0]: zeroPageCount 149508, wiredPagesEncrypted 196385, wiredPagesClear 97772, dirtyPagesEncrypted 634836

18.11.14 00:25:33,000 kernel[0]: hibernate_write_image done(0)

=========================================================================

18.11.14 00:25:33,000 kernel[0]: sleep

18.11.14 00:25:33,000 kernel[0]: Wake reason: RTC (Alarm)

18.11.14 00:25:33,000 kernel[0]: RTC: Maintenance 2014/11/18 01:12:49, sleep 2014/11/17 23:25:33

18.11.14 00:25:33,735 discoveryd[52]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 10.0.0.251 Port 53 errno 50, fd 60, ErrLogCount 1 ResolverIntf:4

18.11.14 02:12:49,000 kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake

18.11.14 02:12:49,000 kernel[0]: AirPort_Brcm43xx::checkInterfacePowerState: Check _pwrOffThreadCall!

18.11.14 02:12:49,000 kernel[0]: Previous sleep cause: 5

18.11.14 02:12:49,000 kernel[0]: AppleThunderboltGenericHAL::earlyWake - complete - took 1 milliseconds

18.11.14 02:12:49,000 kernel[0]: TBT W (1): 0 [x]

18.11.14 02:12:49,303 discoveryd[52]: Basic Bonjour,Warn Warning: IPv4 listener multicast send failed en0, 50

18.11.14 02:12:49,304 discoveryd[52]: Basic Bonjour,Warn Warning: IPv6 listener multicast send failed en0, 50

18.11.14 02:12:50,008 hidd[72]: MultitouchHID: device bootloaded

18.11.14 02:12:54,000 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 1-Gigabit, Full-duplex, No flow-control, Debug [796d,2301,0de1,0300,c1e1,3800]

18.11.14 02:12:54,077 discoveryd[52]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 10.0.0.251 Port 53 errno 49, fd 65, ErrLogCount 2 ResolverIntf:4

18.11.14 02:12:54,078 discoveryd[52]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 10.0.0.251 Port 53 errno 49, fd 65, ErrLogCount 3 ResolverIntf:4

18.11.14 02:12:54,079 discoveryd[52]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 10.0.0.251 Port 53 errno 49, fd 65, ErrLogCount 4 ResolverIntf:4

18.11.14 02:12:54,079 discoveryd[52]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 10.0.0.251 Port 53 errno 49, fd 65, ErrLogCount 5 ResolverIntf:4

18.11.14 02:12:54,080 discoveryd[52]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 10.0.0.251 Port 53 errno 49, fd 66, ErrLogCount 6 ResolverIntf:4

18.11.14 02:12:54,080 configd[26]: LINKLOCAL en0: parent has no IP

18.11.14 02:12:54,964 sharingd[240]: 02:12:54.963 : SDStatusMonitor::kStatusWirelessPowerChanged

18.11.14 02:12:54,988 sharingd[240]: 02:12:54.988 : SDStatusMonitor::kStatusWirelessPowerChanged

18.11.14 02:12:55,896 ntpd[120]: wake time set +0.558865 s

18.11.14 02:13:04,036 SystemUIServer[218]: Menu Extra: <DisplaysExtra: 0x7fadaeb07750> is over retained.

18.11.14 02:13:09,802 Mail[349]: Unable to parse date: "Mon, 20 Oct 2014 19:45"