A few times this week I've arrived at my M1 iMac in the morning only to find the "you are out of system memory" window displayed with a list of everything being paused, and then when I check Activity Monitor I see that "dasd" has basically used up all of my 16 GB of RAM. Anyone else experiencing this at all? It started when I installed beta 2. It's not, like, life-shattering, but it is certainly an inconvenience that I look forward to getting fixed, heh.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Anyone else experiencing "dasd" memory leak on beta 2?
- Thread starter DoctorFedora
- Start date
- Sort by reaction score
bogdanw
macrumors G3
I don't see that here. dasd is a background activity scheduler. Perhaps you've got some background task that is causing the problem?
I'm seeing the same on an M2 Pro mini. Also seeing high CPU usage with dasd and appstoreagent. I have DB2 installed on an MBA too, but I don't have either of these issues on that one.
SketchyClown
macrumors 6502
Not running out of memory here but appstoreagent was causing high CPU usage (250+%) which had dasd also using high CPU (150+%). Killing the process offered temp relief, then it relaunched and immediately was high again. Not good for the battery life on my Air.
Googled around and saw this:
Battery Drain Bug - Golden Gate Beta 2
The "fix" seems to have worked for me so far after a reboot. YMMV.
Googled around and saw this:
Battery Drain Bug - Golden Gate Beta 2
The "fix" seems to have worked for me so far after a reboot. YMMV.
bricktop_at
macrumors 68000
kyrumo
macrumors newbie
I have that on M4 mini with since installing Beta 2 as well. Had one "out of memory" warning. Killing dasd brings things back to normal until it pops up again. Hope this is fixed in the next beta...
ndswrd
macrumors newbie
same here on my base M4 mini, got like three warnings about application memory but i ignored them for some reason. after looking at the activity monitor i saw the dasd process just casually sitting at 33 whole gigabytes of memory. guess ill just have to keep killing the process until beta 3 comes out and potentially fixes this
BaggieBoy
macrumors 6502a
sudo rm -rf /private/var/db/powerlog
sudo reboot
This fixed it for me.
Thanks to Lleweraf on Reddit:
sudo reboot
This fixed it for me.
Thanks to Lleweraf on Reddit:
Well this seems to be doing the trick so far!!! Thank you!
AND, I can see that my system data has gone considerably smaller now as well, 30GB smaller actually. dasd is now using no more than 11 MB a couple hours after rebooting 😊
lungbutter
macrumors member
Some AI slop that may shed light on dasd:
“dasd” stands for Duet Activity Scheduler Daemon. It is part of macOS’s machine learning based prediction system that anticipates which apps you are likely to use next, based on time of day, location, and usage patterns. It works alongside related processes like “duetexpertd” to help the system preload or prioritize resources for apps it predicts you will open soon, which can make app launches feel faster.
It is a normal background system process, not something you Hisneed to worry about or disable, though it can occasionally show up using a bit of CPU during that learning and prediction activity.
If you guys aren’t into AI stuff, I’ll delete it.
Thanks
“dasd” stands for Duet Activity Scheduler Daemon. It is part of macOS’s machine learning based prediction system that anticipates which apps you are likely to use next, based on time of day, location, and usage patterns. It works alongside related processes like “duetexpertd” to help the system preload or prioritize resources for apps it predicts you will open soon, which can make app launches feel faster.
It is a normal background system process, not something you Hisneed to worry about or disable, though it can occasionally show up using a bit of CPU during that learning and prediction activity.
If you guys aren’t into AI stuff, I’ll delete it.
Thanks
at the very least, some sort of indication that you actually verified its veracity in some way, rather than just “I asked ChatGPT or whatever, which anyone could do, and just pasted whatever its output was into here,” might be valuable
Noticed that my M4 Max Studio had written 7.5TB in 6 days, including 220GB by appstoreagent, so I rebooted. Things looked fine, checked back an hour later and I had 55GB of invisible writes. Realized that "my processes" instead of "all processes" was selected in Activity Monitor since when I installed Golden Gate, it was a clean install to a second Volume. Looked again, dasd was taking up 70.6GB, a problem with only 36GB of physical RAM, and kernel_task had written 29GB to SSD.
I ran the command suggested here and that seems to have put a stop to it. dasd is at 7MB.
I really wish Apple could get a handle on these processes that spin out of control and write insane amounts of data to the SSD. Tahoe has had rogue processes do this to me twice and all troubleshooting failed to resolve it. The first time I reinstalled macOS. The second time I installed Golden Gate instead of resetting Tahoe again. Neither of those Tahoe instances were beta versions either so this isn't explicitly a beta bug.
My Studio has written 47TB since I got it last April while reads are sitting at 39TB. Meanwhile my 2TB drive in my Windows desktop I built in 2024 has 55TB of writes and 74TB of reads even though that's my gaming rig where I'm constantly installing 100+GB files and thanks to those large sizes I'm constantly deleting games to make room for new ones, exacerbating the problem if I decide I want to play something I deleted.
At least Apple's rated endurance seems to be much higher. According to S.M.A.R.T. readings, my 2TB 980 Pro is sitting at 96% life remaining after 55TB while my 512GB Studio sits at 99% after 47TB.
I ran the command suggested here and that seems to have put a stop to it. dasd is at 7MB.
I really wish Apple could get a handle on these processes that spin out of control and write insane amounts of data to the SSD. Tahoe has had rogue processes do this to me twice and all troubleshooting failed to resolve it. The first time I reinstalled macOS. The second time I installed Golden Gate instead of resetting Tahoe again. Neither of those Tahoe instances were beta versions either so this isn't explicitly a beta bug.
My Studio has written 47TB since I got it last April while reads are sitting at 39TB. Meanwhile my 2TB drive in my Windows desktop I built in 2024 has 55TB of writes and 74TB of reads even though that's my gaming rig where I'm constantly installing 100+GB files and thanks to those large sizes I'm constantly deleting games to make room for new ones, exacerbating the problem if I decide I want to play something I deleted.
At least Apple's rated endurance seems to be much higher. According to S.M.A.R.T. readings, my 2TB 980 Pro is sitting at 96% life remaining after 55TB while my 512GB Studio sits at 99% after 47TB.
I tried this and it worked for a while, but it appears to just be a temporary fix. Hopefully the next beta will address it.
Comfortably Numb
macrumors regular
Nothing about a system watching your every move to "predict" your next one is normal.
This is the stuff Orwell warned you about.
Comfortably Numb
macrumors regular
GWW3
macrumors newbie
Yes. It has never been an issue for me before this update.
The commands above seem to have helped.