Hi neuroanatomist,
Thank you very much for taking the time to write such a detailed response. I really appreciate it. I definitely don’t want to dismiss any of the possibilities you mentioned. I’d actually like to provide some additional context and some of the troubleshooting I’ve already done, because perhaps something in the results may point you in the right direction.
I’m a software engineer, and this MacBook Pro is one of my primary development machines. It is an M5 Pro with 48 GB of unified memory and a 2 TB SSD, purchased in May 2026.
Before upgrading to macOS 27, I routinely ran a fairly heavy development workload on this machine: Docker containers, VS Code, Python processes, Claude/development tools, browsers, local development services, and several other applications simultaneously. The Mac handled that workload extremely well. Battery life was excellent, performance was excellent, and I did not experience abnormal heating.
For comparison, I have even run a similar development workload on a MacBook Air with only 8 GB of RAM and a 512 GB SSD, and that machine can handle it reasonably well. So the development workload itself does not seem to explain what I am seeing on the M5 Pro.
More importantly, the severe battery drain is happening when I am not running that workload at all.
In one of my recent tests, I left the Mac sleeping and unplugged. It went from approximately 100% battery to 1% over roughly 16 hours, while it was supposed to be sleeping.
I’ve been trying to investigate this from the power-management side rather than just looking at normal application usage.
I checked Activity Monitor for unusual CPU and memory activity and have not found a persistent user application consuming resources at a level that would explain this kind of overnight drain.
I also checked the actual free disk space, and storage capacity is not an issue. This machine has a 2 TB SSD with plenty of actual free space.
I then started looking at pmset and the sleep/wake logs.
Running:
pmset -g assertions
did not show a permanent application or system process preventing sleep. In the results I saw:
- PreventSystemSleep = 0
- BackgroundTask = 0
- NetworkClientActive = 0
There were some temporary assertions, including one from coreaudiod associated with the built-in speakers, as well as Handoff/network-related activity and a kernel MAGICWAKE assertion associated with IOSkywalkNetworkBSDClient, but nothing that appeared to be a permanent sleep blocker.
My power-management settings also showed:
- powernap = 1
- tcpkeepalive = 1
- womp = 0
- standby = 1
- hibernatemode = 3
When I looked deeper into the sleep/wake history, however, things became more interesting.
The logs showed a fairly large number of sleep/wake events, including 225 Sleep/Wakes since boot, and one sleep cycle showed 7 Dark Wakes.
I also found repeated background wake activity involving things such as:
- TCPKeepAlive
- Wi-Fi/Bluetooth activity (wifibt)
- mDNSResponder
- dasd
- PowerUIAgent
- Apple Intelligence-related background tasks
- maintenance wakes
- scheduled wake requests
Some of the scheduled/background activity included com.apple.intelligenceflow.toolbox.update.fastpass, Screen Time persistent-history cleanup, PowerUIAgent maintenance activity, mDNS/DHCP renewal, and other system maintenance events.
I also saw powerd creating an InternalPreventSleep assertion associated with:
com.apple.powermanagement.darkwakelinger
which later timed out.
So at this point, what I am trying to understand is whether the Mac is technically entering sleep but waking repeatedly in the background, which could explain both the battery drain and why the computer sometimes feels warm even though I am not actively using it.
This is also why I’m having a hard time attributing the problem simply to my development software. The same applications and essentially the same workload were present before macOS 27, but this behavior only appeared after the upgrade.
I also understand your point that your M4 Pro is running macOS 27 without battery problems. That is useful information because it suggests this may not affect every Mac running macOS 27. I’m wondering whether there could be something specific to the M5/M5 Pro platform, a particular system service, or some power-management behavior triggered by the upgrade.
It has also been almost a week since the upgrade, so although I understand that Spotlight, Photos, Apple Intelligence, iCloud, and other services can perform extensive background work after a major OS update, I would have expected that activity to settle down by now.
If you have experience interpreting the pmset sleep/wake logs, I would really appreciate your thoughts on the repeated DarkWake activity. If there are any additional commands, logs, or specific sections of an EtreCheck report that you think would be useful, I’d be happy to run them and post the results.
Thanks again for your help and for taking the time to provide such a detailed response.