I encountered an unusual and perplexing issue today with VoiceOver, one that I believe warrants attention and collective insight from our community. While using Safari, I noticed that it became completely unresponsive—a problem encounter daily but never thought of investigating it further. What truly caught my attention, however, was the profound impact this had on my Mac's overall performance.
As many of us are aware, VoiceOver, Typically, operates with remarkable efficiency, utilizing an average of 10 to 40 units of energy (as measured in the Energy Impact section of the Activity Monitor). However, today's experience was far from typical.
When Safari became unresponsive, VoiceOver's Energy Impact suddenly surged to an astonishing 4000 units—an alarming departure from its usual behavior. While the specific unit of measurement remains unclear to me, this surge was exceptional and had an adverse effect on my Mac's performance, causing it to overheat, and more significantly for Safari not to respond in a crucial moment of my work.
Here's where it gets even more intriguing: I attempted to troubleshoot the issue by turning VoiceOver off and then back on. To my surprise, this seemingly simple action resulted in a significant reduction in the Energy Impact, which dropped to a more manageable level of around 20 units.
This observation has left me both baffled and intrigued. I've noticed similar reports of this issue in various forums, indicating that I'm not alone in experiencing this anomaly. It's a concern not only because it disrupts our Mac's performance but also because it could potentially have long-term implications for the hardware.
I will report this to Apple Accessibility, so please do report the same findings if you find the above applicable to your experience.