<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MacOS on Frank Zhang: Engineering Notes</title><link>https://www.fzhang.dev/en/categories/macos/</link><description>Recent content in MacOS on Frank Zhang: Engineering Notes</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 09 Nov 2026 10:00:00 +0800</lastBuildDate><atom:link href="https://www.fzhang.dev/en/categories/macos/index.xml" rel="self" type="application/rss+xml"/><item><title>corespotlightd high CPU on Mac: read-only diagnosis before you delete anything</title><link>https://www.fzhang.dev/en/posts/corespotlightd-high-cpu/</link><pubDate>Mon, 09 Nov 2026 10:00:00 +0800</pubDate><guid>https://www.fzhang.dev/en/posts/corespotlightd-high-cpu/</guid><description>High CPU from corespotlightd is a reason to look first. These notes do not treat deleting the Spotlight index, or CoreDuet, as the starting step.</description></item></channel></rss>