Memory leaks in macOS Monterey plague small number of users
AppleInsider is supported by its audience and may earn commission as an Amazon Associate and affiliate partner on qualifying purchases. These affiliate partnerships do not influence our editorial content.
Complaints about memory leaks have started to surface following the release of macOS Monterey to the public, with users discovering unusually high amounts of memory being consumed by apps.
The release of a new operating system is typically accompanied by a period of teething issues, with users and developers discovering small issues that are later adjusted or fixed by Apple. On Monday, reports about memory leaks started to surface, specifically among Mac users who upgraded to macOS Monterey.
A memory leak is an issue when an application or a process falters and fails to release allocated memory properly. Over time, this could cause a service or an app to consume vast amounts of memory, reducing the resources available for use by others.
A number of complaints have been found on social media and the Apple Support forum, as initially reported by Macrumors, where users encounter the problem on their own Macs, running on macOS Monterey.
In the case of YouTube personality Tyler Stalman, he claims to repeatedly get warnings on his M1 Max-equipped MacBook Pro. The warning states he has “run out of application memory” with macOS advising to force quit memory-hogging applications, such as his 24GB instance of Final Cut Pro.
On Reddit, one user posted an Activity Monitor screenshot showing Control Center as occupying 9.19GB of memory, a macOS service that usually only consumes a few megabytes. A similar issue was noticed by Gregory McFadden on Twitter, with Control Center consuming over 26GB.
Another from Twitter posted an image on October 27 with the same out-of-memory warning window, with Firefox using 79.20GB of memory.
While an irritant for those affected, there are still only relatively few complaints about the memory leaks in macOS Monterey. The low number of reports about the issue points to it being quite rare for users to experience, rather than an epidemic affecting many users in a major way.