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.

Well the messages in console returned so I guess the external drive analysis was wrong. Was OK for 4 days then they returned so not sure where to look now.

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.

Thanks! This and the response from 'Barney-15E' seem like the most logical explanation. I won't worry about the entries any longer...

Joe

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.

And how you do that? set all you progress indicators to false?

Did you ever get an answer for this problem? I have just an iPhone 5S, it's nothing special and I've got excessive wake ups in my diagnostics. My phone has been doing weird things