
The cause has now been isolated to a single group of settings in one preference pane, Accessibility. Neither was there any evidence of kernel or Mach zone memory leaks. What was perhaps most surprising was that some users were severely affected, but most users weren’t affected at all and could use the same apps for days without any significant change occurring in their memory use. At first this appeared confined to certain apps, including Firefox, Microsoft Word, and even Safari. Soon after the release of macOS 12.0.1, reports appeared that some apps, notably Firefox, could suffer large and progressive memory leaks until they took 70 GB or more of app memory, and the Mac simply ran out. This article explains how it occurs, and how you can prevent it from happening on your Mac. Thanks to the work of the engineers at Mozilla, its cause has now been identified, and I’m very grateful to fujimidai1 who has pointed this out to me. You will no doubt have heard of the claimed memory leak in macOS Monterey 12.0.1.
