[{"data":1,"prerenderedAt":278},["ShallowReactive",2],{"post-en-fixing-macos-high-cpu-usage-in-dasd-process-with-antigravity":3,"surround-en-blog\u002Fen\u002Fblog\u002Ffixing-macos-high-cpu-usage-in-dasd-process-with-antigravity.md":265},{"id":4,"title":5,"body":6,"canonical":15,"category":249,"date":250,"description":251,"extension":252,"image":253,"meta":254,"navigation":255,"path":256,"seo":257,"slug":258,"status":259,"stem":260,"tags":261,"translationSlug":258,"__hash__":264},"blog\u002Fen\u002Fblog\u002Ffixing-macos-high-cpu-usage-in-dasd-process-with-antigravity.md","Fixing macOS High CPU Usage in dasd Process with Antigravity",{"type":7,"value":8,"toc":239},"minimark",[9,17,32,37,40,45,54,56,60,65,77,91,93,97,100,167,172,178,180,184,190,229,231,234],[10,11,12],"p",{},[13,14],"img",{"alt":15,"src":16},"","\u002Fimages\u002Fposts\u002F2026\u002F09\u002Fimage-1024x576.png",[10,18,19,20,27,28,31],{},"Today, my Mac (running the latest macOS 27.0 beta 8) suddenly started lagging. Opening Activity Monitor revealed that a system process named ",[21,22,23],"strong",{},[24,25,26],"code",{},"dasd"," was pinning a single CPU core at 90%–120%. A quick search yielded no useful answers. Tracing it down with Google Antigravity, I uncovered a hilarious blunder: ",[21,29,30],{},"an infinite loop caused by an Apple engineer handling time zones incorrectly",".",[10,33,34],{},[13,35],{"alt":15,"src":36},"\u002Fimages\u002Fposts\u002F2026\u002F09\u002Fimage-1-1024x685.png",[38,39],"hr",{},[41,42,44],"h2",{"id":43},"tldr-run-this-command-directly","TL;DR — Run this command directly:",[46,47,52],"pre",{"className":48,"code":50,"language":51},[49],"language-text","defaults write com.apple.appstored ArcadePayoutResetDate \\\n  -date \"$(date -v+3d -u +\"%Y-%m-%dT%H:%M:%SZ\")\" && \\\n  killall appstoreagent\n","text",[24,53,50],{"__ignoreMap":15},[38,55],{},[41,57,59],{"id":58},"troubleshooting-process-with-google-antigravity","Troubleshooting Process with Google Antigravity",[61,62,64],"h3",{"id":63},"conclusion-current-status-bluf","Conclusion & Current Status (BLUF)",[10,66,67,69,70,31],{},[24,68,26],{}," continuously consuming 90%–99% CPU is ",[21,71,72,73,76],{},"not routine background system maintenance, but rather ",[24,74,75],{},"appstoreagent"," (the App Store background daemon) trapped in a hyperactive scheduling loop",[10,78,79,80,83,84,86,87,90],{},"The root cause has been isolated and ",[21,81,82],{},"resolved",". CPU usage for ",[24,85,26],{}," dropped from ",[21,88,89],{},"98.1% to 0.0%",", and the system returned to normal without requiring a reboot.",[38,92],{},[61,94,96],{"id":95},"root-cause-analysis","Root Cause Analysis",[10,98,99],{},"Unified Logging System captures and process call traces provided clear evidence of the infinite loop:",[101,102,103,114],"ol",{},[104,105,106,109,110,113],"li",{},[21,107,108],{},"Offending Task",": ",[24,111,112],{},"com.apple.appstored.ArcadeResetPO"," (Apple Arcade payout metrics reset task).",[104,115,116,119,120],{},[21,117,118],{},"Logic Flaw",":\n",[121,122,123,138,147,157],"ul",{},[104,124,125,126,129,130,133,134,137],{},"The actual current time was in the afternoon, but ",[24,127,128],{},"ArcadePayoutResetDate"," in ",[24,131,132],{},"com.apple.appstored"," preferences was pinned to midnight earlier that day: ",[24,135,136],{},"2026-09-06 00:00:00 +0800"," (a timestamp in the past).",[104,139,140,141,143,144,31],{},"After finishing the reset, ",[24,142,75],{}," failed to advance the timestamp to the next cycle (the following day). Instead, it re-registered the task using the already expired timestamp ",[24,145,146],{},"2026-09-06 00:00:00",[104,148,149,150,152,153,156],{},"When ",[24,151,26],{}," (Duet Activity Scheduler) received the registration, it saw that the scheduled execution time was in the past, marked it as overdue, and triggered it immediately (",[24,154,155],{},"Running immediately on submission",").",[104,158,159,160,163,164,166],{},"Outcome: ",[21,161,162],{},"Over 400 dispatch and IPC events triggered per second",", keeping ",[24,165,26],{}," pegging a full CPU core continuously.",[168,169,171],"h4",{"id":170},"unified-log-trace","Unified Log Trace",[46,173,176],{"className":174,"code":175,"language":51},[49],"appstoreagent: [ArcadePayoutReset] Payout metrics reset with current payout reset time: 2026-09-06 00:00:00+0800\nappstoreagent: [ArcadePayoutReset] Reset with reason: Rescheduling\nappstoreagent: [ArcadePayoutReset] Using new date: 2026-09-06 00:00:00+0800 with reason: Rescheduling\nappstoreagent: [ArcadePayoutReset] Activity not scheduled; submitting request\ndasd:          SUBMITTING: 501:com.apple.appstored.ArcadeResetPO\ndasd:          Running immediately on submission\ndasd:          REQUESTING START: 501:com.apple.appstored.ArcadeResetPO\n",[24,177,175],{"__ignoreMap":15},[38,179],{},[61,181,183],{"id":182},"mitigation-verification","Mitigation & Verification",[10,185,186,187,189],{},"The loop was broken by manually pushing the scheduled date forward in user defaults and gracefully restarting ",[24,188,75],{},":",[101,191,192,200],{},[104,193,194,109,197],{},[21,195,196],{},"Command Executed",[24,198,199],{},"defaults write com.apple.appstored ArcadePayoutResetDate -date \"2026-09-06T16:00:00Z\" && killall appstoreagent",[104,201,202,119,205],{},[21,203,204],{},"Verification Results",[121,206,207,223],{},[104,208,209,210,213,214,109,217,219,220,31],{},"Monitored via ",[24,211,212],{},"top"," \u002F ",[24,215,216],{},"ps",[24,218,26],{}," (PID 404) CPU usage instantly fell to ",[21,221,222],{},"0.0%",[104,224,225,226,228],{},"After restarting, ",[24,227,75],{}," suspended normally and stopped flooding the system log at 400+ entries\u002Fsec.",[38,230],{},[10,232,233],{},"After working through the trace with Google Antigravity, CPU usage is back to normal.",[10,235,236],{},[13,237],{"alt":15,"src":238},"\u002Fimages\u002Fposts\u002F2026\u002F09\u002Fimage-2-1024x692.png",{"title":15,"searchDepth":240,"depth":240,"links":241},2,[242,243],{"id":43,"depth":240,"text":44},{"id":58,"depth":240,"text":59,"children":244},[245,247,248],{"id":63,"depth":246,"text":64},3,{"id":95,"depth":246,"text":96},{"id":182,"depth":246,"text":183},"coder","2026-09-08","Today, my Mac (running the latest macOS 27.0 beta 8) su ...","md","\u002Fimages\u002Fposts\u002F2026\u002F09\u002Fimage.png",{},true,"\u002Fen\u002Fblog\u002Ffixing-macos-high-cpu-usage-in-dasd-process-with-antigravity",{"title":5,"description":251},"fixing-macos-high-cpu-usage-in-dasd-process-with-antigravity","publish","en\u002Fblog\u002Ffixing-macos-high-cpu-usage-in-dasd-process-with-antigravity",[262,263],"beta","macos","Z2gwzgjRQIQZt9hmVPVPqIX0DEz96lXSI12rgf7GUEk",[266,272],{"title":267,"path":268,"stem":269,"slug":270,"date":271,"children":-1},"Frontier Engineering: 10 Core Principles","\u002Fen\u002Fblog\u002Ffrontier-engineering-ten-core-principles","en\u002Fblog\u002Ffrontier-engineering-ten-core-principles","frontier-engineering-ten-core-principles","2026-09-10",{"title":273,"path":274,"stem":275,"slug":276,"date":277,"children":-1},"Antigravity 2.12.0 Introduces the \u002Fboost Command","\u002Fen\u002Fblog\u002Fantigravity-2-12-0-boost-command","en\u002Fblog\u002Fantigravity-2-12-0-boost-command","antigravity-2-12-0-boost-command","2026-09-03",1791430076838]