Hello, my computer randomly starts it's fan and then starts to deplete the battery extremely quickly even when I'm running only a few tabs (5 tabs plus notion). I would say it lasts 90 minutes when it acts like this which is frustrating. I've included the EtreCheckPro analysis. Please help, this mac is not that old and this has been happening for about 10 months at this point.
[Re-Titled by Moderator]
MacBook Pro 13″, macOS 15.3
You hard drive scores are well under what I expect to see, especially the Write speed. It should never be under 1000MB/sec on a Mac with a factory SSD. Both should be over about 1800-2000MB/sec.
That slowness could be related to your SSD having only ~11 percent free space.
The last version of Norton that did not cause issues with Macs was released about 1999. You need to get rid of it because it could be masking other issues.
John got right; I misread:
Top Processes Snapshot by Memory:
Process (count) RAM usage (Source - Location)
EtreCheckPro 622 MB (Etresoft, Inc.)
Notion 335 MB (Notion Labs, Incorporated)
kernel_task 264 MB (Apple)
Notion Helper (Renderer) (6) 263 MB (Notion Labs, Incorporated)
Google Chrome Helper (Renderer) (5) 253 MB (Google LLC)
Mea cupla.I was not at my usual workstation and am still adjusting to which computer glasses work best with my new Macbook Pro.
My colleagues are being Far Kinder to you than appropriate for this disasterous situation.
You are using an intel Mac with only 8 GB or RAM to do FAR too much. User experiences here tells us a Mac with 8 GB or less attempting to run MacOS Ventura or later simply can not perform ordinary tasks in a reasonably responsive way.
The only known way to get productivity on such a computer is to drop back to 'ONE App at a time' operation, quit one App completely before launching the next. Restart frequently.
Your disk is Utterly and completely FULL. 11 percent remaining means that when your wildly undersized RAM memory fills up, your Mac 'fakes' the rest of the required RAM in a SWAP file on the Boot Drive. In your case, with essentially NO space left on the drive, you Mac slows to a very slow crawl. As others observed, that is the reason your disk tests extremely slow. You need FAR more disk drive space.
Docker sounds like a great idea, until you look into "how does it do these tricks?" The answer is that it loads a version of Linux, and creates all the 'Docked' items inside ANOTHER Operating System attempting to run UNDER your MACOS, which is already starved for resources and can not get out of its own way at the moment due to far too little RAM AND no disk space.
The punchline:
If you want to Run Docker, or practically ANYTHING more complex than a web Browser OR Mail, loaded one at a time, you need a more capable computer.
At this writing, Apple does not sell a Mac with only 8GB RAM or with such a small Boot drive. but almost ANY Apple-silicon Mac, including MacBook Air models, can run circles around what your current Mac COULD do when it was in its Prime.
After some further research I think it may be some issue with the icdd. I will try fixes with that once it presents itself again. I deleted it directly from activity monitor and it instantly fixed itself
See if the Kernel Panic log still exists and post it here using the "Additional Text" icon which looks like a piece of paper on the forum editing toolbar. Kernel Panic logs are located in "/Library/Logs/DiagnosticReports" and possibly even the "Retired" subfolder with "kernel" and/or "panic" in the file name.
Run Disk Utility First Aid on the hidden Container. Within Disk Utility you may need to click "View" and select "Show All Devices" before the hidden Container appears on the left pane of Disk Utility. Even if the First Aid summary says everything is "Ok", click "Show Details" and scroll through the report to see if any unfixed errors are listed. If there are any errors, then run First Aid again until the errors are gone. If after several scans the errors remain, then run First Aid while booted into Recovery Mode.
I don't use Docker, but I did see another respected contributor in another Apple forum thread mention Docker could be a possible issue.
Besides possibly running low on the Free storage space as mentioned by @Allan Jones, there is also a possibility you may be running low on memory at times since the report does show about 1.6GB of Swap....perhaps this gets worse under some other workloads or when the laptop has not been rebooted for a while. The information in the EtreCheck report was for system details occurring in less than a day.
FYI, the Free storage value is only shown in Disk Utility or the System Profiler. Unfortunately the "Available" value shown everywhere within macOS is very misleading. With macOS storage Free is not a synonym for "Available". Notice the difference between them in the EtreCheck report (29.84GB vs 112.19GB).
Allan Jones wrote:
The last version of Norton that did not cause issues with Macs was released about 1999. You need to get rid of it because it could be masking other issues.
Just curious where you saw Norton in this EtreCheck report. I looked through it twice & did not notice it. Is it me or is it you?
Running First Aid on “Container disk1”
Verifying the startup volume will cause this computer to stop responding.
Verifying storage system
Using live mode.
Performing fsck_apfs -n -x -l /dev/disk0s2
Checking the container superblock.
Checking the checkpoint with transaction ID 9389701.
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking the encryption key structures.
Checking volume /dev/rdisk1s1.
Checking the APFS volume superblock.
The volume Macintosh HD was formatted by storagekitd (2313.41.1) and last modified by apfs_kext (2317.81.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking snapshot 1 of 1 (com.apple.os.update-3248D6DF56F40ADEEC4BC80CC7573F3A1D092E3F436F3F63B68C2B4E287608FC, transaction ID 8567170)
Checking the fsroot tree.
Checking the file extent tree.
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s1 with UUID 2E549716-1B97-4747-B5E7-5287567A2AE6 appears to be OK.
Checking volume /dev/rdisk1s2.
Checking the APFS volume superblock.
The volume Macintosh HD - Data was formatted by asr (1412.141.1) and last modified by apfs_kext (2317.81.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the document ID tree.
Checking the fsroot tree.
warning: inode (id 27060060): Resource Fork xattr is missing or empty for compressed file
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s2 with UUID 53DACBE6-78D7-4309-9DC2-396476847CE7 was found to be corrupt and needs to be repaired.
Checking volume /dev/rdisk1s3.
Checking the APFS volume superblock.
The volume Preboot was formatted by asr (1412.141.1) and last modified by apfs_kext (2317.81.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the fsroot tree.
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s3 with UUID 044897B0-BF21-4C1D-839E-E744E95D8121 appears to be OK.
Checking volume /dev/rdisk1s4.
Checking the APFS volume superblock.
The volume Recovery was formatted by asr (1412.141.1) and last modified by apfs_kext (2317.81.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the fsroot tree.
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s4 with UUID 1909AE6E-BCB6-45F6-BA29-775266655C1D appears to be OK.
Checking volume /dev/rdisk1s5.
Checking the APFS volume superblock.
The volume Update was formatted by com.apple.MobileSof (2313.41.1) and last modified by apfs_kext (2317.81.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the fsroot tree.
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s5 with UUID F2179C2C-FE65-4070-AD57-A235F399167B appears to be OK.
Checking volume /dev/rdisk1s6.
Checking the APFS volume superblock.
The volume VM was formatted by com.apple.MobileSof (2313.41.1) and last modified by apfs_kext (2317.81.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking the fsroot tree.
Checking the extent ref tree.
Verifying volume object map space.
The volume /dev/rdisk1s6 with UUID 8274E6FE-EC33-491B-B1A9-DC003D91118A appears to be OK.
Verifying allocated space.
Performing deferred repairs.
warning: need to clear bsd flags (0x20) in inode (object-id 27060060)
warning: found orphan/invalid xattr (id 27060060, name com.apple.decmpfs)
The container /dev/disk0s2 appears to be OK.
Storage system check exit code is 0.
Operation successful.
This is my DiagnosticsReports folder:
CloudServicesTopic_2025-04-18-103603_Peytons-MacBook-Pro.diag
CloudServicesTopic_2025-04-21-151954_Peytons-MacBook-Pro.diag
KeySyncTopic_2025-04-18-103603_Peytons-MacBook-Pro.diag
KeySyncTopic_2025-04-21-151954_Peytons-MacBook-Pro.diag
NetworkingTopic_2025-04-18-103603-1_Peytons-MacBook-Pro.diag
NetworkingTopic_2025-04-18-103603_Peytons-MacBook-Pro.diag
NetworkingTopic_2025-04-21-151954_Peytons-MacBook-Pro.diag
Retired
proactive_event_tracker-com_apple_Trial-com_apple_triald_2025-04-16-140908_Peytons-MacBook-Pro.diag
proactive_event_tracker-com_apple_Trial-com_apple_triald_2025-04-18-103611_Peytons-MacBook-Pro.diag
proactive_event_tracker-com_apple_Trial-com_apple_triald_2025-04-21-161009_Peytons-MacBook-Pro.diag
proactive_event_tracker-com_apple_Trial-com_apple_triald_2025-04-22-083221_Peytons-MacBook-Pro.diag
Retired is empty.
I tried the First AID and didn't see any errors except maybe it could not be unmounted. I didn't see a hidden Container:
Running First Aid on “Macintosh HD” (disk1s1s1)
Verifying the startup volume will cause this computer to stop responding.
Verifying file system.
Volume could not be unmounted.
Using live mode.
Performing fsck_apfs -n -l -x /dev/rdisk1s1
Checking the container superblock.
Checking the checkpoint with transaction ID 9390061.
Checking the EFI jumpstart record.
Checking the space manager.
Checking the space manager free queue trees.
Checking the object map.
Checking the encryption key structures.
Checking volume /dev/rdisk1s1.
Checking the APFS volume superblock.
The volume Macintosh HD was formatted by storagekitd (2313.41.1) and last modified by apfs_kext (2317.81.2).
Checking the object map.
Checking the snapshot metadata tree.
Checking the snapshot metadata.
Checking snapshot 1 of 1 (com.apple.os.update-3248D6DF56F40ADEEC4BC80CC7573F3A1D092E3F436F3F63B68C2B4E287608FC, transaction ID 8567170)
Checking the fsroot tree.
Checking the file extent tree.
Checking the extent ref tree.
Verifying volume object map space.
Verifying allocated space.
The volume /dev/rdisk1s1 with UUID 2E549716-1B97-4747-B5E7-5287567A2AE6 appears to be OK.
File system check exit code is 0.
Restoring the original state found as mounted.
Operation successful.
I think this issue started before Docker.
I don't really understand what the rest of what you're saying in the last 2 paragraphs.
The issue I'm having makes it really difficult to use my mac when I'm not near a port so I hope you can help me!
I think it was a misreading of the "Notion" app.
How can I prevent my MacBook Pro from battery deplete issue?
