Excessive Wakeups

Yes. This is an old topic concerning EyeTV and is unrelated to McAfee. Like all commercial "anti-virus" products it serves no beneficial purpose on a Mac, and belongs in the Trash.

This site was recently upgraded and I'm finding an unexpectedly large number of new replies to old questions, sometimes much older than this one. I don't believe that was the intended result of the upgrade. May I ask how you found this question, and what led you to replying to it, instead of posting your own question? If you don't want to explain that's fine, but if a common reason can be determined I'll pass it along to those who may be able to fix it.

I searched for "excessive wake ups" as these were the key words in the Console listing. I usually try to search the forums for related topics before posting a new issue as I see too much of that by others. I realized this particular question largely related to the Eye TV users, but it appeared that others had similar problems with other software. I'll delete the McAfee and hope that resolves it. As I said, it's more of a nuisance issue than a real problem.

Thanks. I think the problem is that this site's new format encourages searching for similar questions before posting a new one. That's beneficial, but more often than not, the initial results of the search are outdated, often by years. That's not good.

In your case, the problem is almost certainly McAfee. Get rid of it. If you aren't certain how to do that by all means post a new question, which is sure to solicit more interest.

None of this seems to create any kind of problem - just an aggrivation.

Any idea what is going on here?

Unless a message is repeating infinitely, just because it shows up in Console doesn’t indicate a problem.

The messages in Console are not intended for the user. They are for the developers to monitor their software.

Here is a succinct explanation from Marcel Bresink in the help docs for his software.

http://www.bresink.com/osx/0SystemMonitor/Docs-en/pgs/0350-TWakeups.html

These messages and reports are normal. They neither indicate a problem with the computer or the App. They only indicate that System Monitor is using services of the operating system core (kernel) more often as OS X is expecting it for average applications. Software developers can use such reports to reduce the energy consumption created by Apps.

I get the same messages. Mostly using Google Chrome but sometimes when I use Parallels or Toast. I see no functional issues just these messages which are kind of annoying. If I did not go into the Console I would not even know about these.

I figured it out. I never paid much attention before (and most users wouldn't either) but I noticed that I have getting some console messages indicating "wakeups resource spin" if I started an application and noticed my external USB hard drive would start to spin up. I was using this as my Time machine and it would spin down between backups but for no apparent reason would spin up if starting various programs. Tried every possible fix but no luck keeping it from spinning up. I then decided to keep my drive spinning except when my Mac would sleep or shut down at night. Now no more messages. I wonder if Apple did this with FW drives to preclude these logs as well. I figured since my TM drive had to spin up every hour anyway it might as well just stay spinning in between. I do not expect much wear from this approach.

Believe it or not, I have actually discovered what is causing this. Being an OSX developer my apps suddenly started to result in those excessive wakeups and it took quite a while and a lot of debugging to figure it out.

Anyway, it turns out that if you have indeterminate NSProgressIndicators (those small rotating progress indicators) in your app and they are visible longer than 300 seconds then the app hangs and you get one of those posts in the console log. I set all my progress indicators to false insted of true and the problem was gone. I have verified this on three machines running and with five applications. Certainly seems like a OSX bug.

I began have 'issues' a few weeks ago. Several times MSWord failed Autosaves - saying the disk was full (the SSD is only 50% full). I ran the Disk Utility and nothing showed. Then I had two complete system crashes to a black screen (from within Firefox) followed by immediate auto-restarts which 'seemed' to recover everything that I was actively working on. I started looking at the console logs to see if there was anything clearly out of sorts. Indeed, there were many diagnostic reports from Microsoft and Firefox (Excessive Wakeups) and the Microsoft Autosave event generated a cpu report (96% cpu over 94 seconds). I understand that these are mostly tools for code developers, but these reports ramped up as my performance ramped down (I know ... correlation does not prove a connection)

Following the suggestion from an Apple Support tech (I'm still on Apple Care), I reset the SMC (shift-enter-option-pwr) and reset the PRAM. He suggested that I try this and see it things improve. fwiw - the logs have been clear of these excessive wakeups and there have been no system crashes in the past week of heavy use. Knock on wood.

timestamp":"2017-03-22 02:32:10.66 -0400","bug_type":"142","os_version":"iPhone OS 10.2.1 (14D27)","incident_id":"0BFB5382-E1C6-48D4-A4D5-CE14FE4A60B1"}

Date/Time: 2017-03-22 02:27:22 -0400

OS Version: iPhone OS 10.2.1 (Build 14D27)

Architecture: arm64

Report Version: 19

Command: amy

Path: /var/containers/Bundle/Application/A1224398-960F-440D-9829-0BDE10667449/amy.app /amy

Version: 3165 (3165)

Parent: launchd [1]

PID: 1415

Event: wakeups

Wakeups: 45001 wakeups over the last 288 seconds (156 wakeups per second average), exceeding limit of 150 wakeups per second over 300 seconds

Duration: 287.81s

Steps: 126

Hardware model: iPhone8,1

Active cpus: 2

Powerstats for: amy [1415]

UUID: 5E052756-E8AA-3251-9A30-7CB8C61B9EFF

Start time: 2017-03-22 02:30:57 -0400

End time: 2017-03-22 02:32:10 -0400

Parent: launchd

Microstackshots: 126 samples (100%)

Primary state: 77 samples Frontmost App, User mode, Effective Thread QoS User Interactive, Requested Thread QoS User Interactive, Override Thread QoS Unspecified

User Activity: 0 samples Idle, 126 samples Active

Power Source: 126 samples on Battery, 0 samples on AC

79 ??? (libdyld.dylib + 17848) [0x188c795b8]

79 ??? (+ 181424) [0x1000d44b0]

79 ??? (UIKit + 480564) [0x18fcd8534]

79 ??? (UIKit + 501756) [0x18fcdd7fc]

79 ??? (GraphicsServices + 49560) [0x18b74a198]

79 ??? (CoreFoundation + 37560) [0x189c962b8]

78 ??? (CoreFoundation + 898044) [0x189d683fc]

78 ??? (CoreFoundation + 907280) [0x189d6a810]

78 ??? (libdispatch.dylib + 23912) [0x188c4ad68]

78 ??? (libcorecrypto.dylib + 405948) [0x188c461bc]

78 ??? (libcorecrypto.dylib + 406012) [0x188c461fc]

78 ??? (

My phone has been doing weird things

Those messages have nothing to do with the functioning of your Mac or iPhone. Like virtually everything in the console, they are messages for developers so that they can optimize their apps.

Start a separate post in the iPhone community with details about the problem you are having, not what you think it might be causing the problems.

This is the first thing that came up in a search for excessive wakeups.

This is certainly a bug and not something to just toss aside as something "too advanced" for us dull, silly end-users.

For a couple months, I've been having extreme issues with my 2010 Mac Pro - 12 core 3.46 ghz Xeon, 128 gb/1 tb/GTX1080. Also have two internal 4tb storage drives and an external 4 tb Time Machine volume.

I've noticed some extreme lag in the UI if I let it sit for a few minutes without usage. To the point where even switching between apps might take a full minute as the image chops across the screen. In addition, I've had several full lockups, requiring a forced restart, and many times losing anything that wasn't autosaved. Latest one caused the screen to go all black. Even the screen saver will sometimes drop to only a frame or two a second, and if I wake it up while that's happening, it will take 5-7 minutes for the system to be usable again. Several apps are having a very hard time - Twitter, VMWare, Safari and iTunes are all extremely sluggish and even crash.

I've noticed that the window server as well as the above apps all generate excessive wakeup request reports, and I've gone back and looked at the time stamps and many seem to have happened during a particular bad slowdown/crash. OS X has a hard limit of 150 wakeups per second on a thread, some threads by the above apps (and others) are exceeding 45,000 a second. Quite obvious to anyone who understands how OS X works, this is a bug and will certainly cause problems.

By the way, I'm running 10.12 at the moment, so this bug is still apparently in the system. I will try an SMC reset and see if that solves the problem. Haven't done one in over a year on this machine so I suppose it was due for one anyway.

I feel it's far more helpful to actually analyze and troubleshoot this problem than to summarily dismiss it as something that's far too complex for us to possibly understand...I've lost work due to this bug and it has severely impacted my productivity. Not acceptable for a Pro machine running an up-to-date version of OS X with no questionable third-party software and obsessive-compulsive maintenance.

I hope it gets resolved in a future update.

Apple will never resolve a problem caused by a garbage "anti-virus" program such as McAfee.

Writing an effective Apple Support Communities question

I will add to this as well, not much on the web about this error in console.

Is this for debugging purposes, or a bad app.

Type this into terminal

syslog | grep -i "Wake Reason"

you can see the reasons the mac was awaken. Could be alarms (crontab entries), could be network access, could be keyboard/mouse/trackpad stuff.

I found this,

Reset SMC

Shut down

Safe boot

Shut down

Reset PRAM.

Set pier options to defaults.

Helped with many apps.

Let's see if they come back.

I think there is a bug in sleep mode.