Mastodawn

Today’s update to macOS Tahoe (26.0.1) resolves an issue in apps where AutoFill for Mac apps could make apps slow down over time due to improper handling of event taps, causing them to accumulate over time. People particularly noticed this in Chromium-based web browsers and Electron apps

Performance should be better now, but if your Mac app will never, ever benefit from offering AutoFill of security codes received via Messages or Mail, the right way to do it is this supported Info.plist key: https://developer.apple.com/documentation/bundleresources/information-property-list/nsautofillrequirestextcontenttypeforonetimecodeonmac

NSAutoFillRequiresTextContentTypeForOneTimeCodeOnMac | Apple Developer Documentation

A Boolean value that indicates whether text fields receive AutoFill of one-time codes only if they adopt the suitable content type.

Apple Developer Documentation

neofox_rainbow_256

🔜EF30 Sep 29, 2025

@rmondello why looks this key-name as if it was from a Java developer

Ricky Mondello Sep 30, 2025

@morihofi It was written by me, a Cocoa developer. :)

Jeroen Sep 30, 2025

@rmondello Could it be that whatever got fixed is in macOS 15.7.1 as well? Because Safari was truly a laggy mess in 15.7 on M1 Max MacBook Pro. Seconds of input delay in URL bar. I hope it is fixed.

Ricky Mondello Sep 30, 2025

@jeroen This issue did not affect non-macOS 26 builds of macOS. It also didn't affect Safari.

Jeroen Sep 30, 2025

@rmondello argh, too bad then. I had my hopes up! :)

David Chisnall (*Now with 50% more sarcasm!*)Sep 30, 2025

Huh, SWT had a similar bug in their Cocoa back end in the early OS X days. They registered a repeating timer instead of a one-shot one, so the number of timers would gradually increase. If you left a SWT app doing nothing, its CPU usage would gradually climb to 100%. And all of that was waking for timers, seeing there was nothing to do, and reentering the event loop.

Ricky Mondello Sep 30, 2025

@david_chisnall In this case, events firing themselves triggered the accumulation of more event monitors. Wild stuff.

Andrew Laurence Sep 30, 2025

@rmondello Is this why, for a while now, Slack would sometimes spinlock for no apparent reason? (Predating Tahoe.)

Ricky Mondello Sep 30, 2025

@atlauren Not predating Tahoe.

@rmondello is this fix in the 26.1 beta too?

Ricky Mondello Oct 1, 2025

@gsapienza Not yet.

@rmondello got it thanks!

@rmondello Unfortunately, this fix doesn’t help Chromium. The issue is that NSAutoFillHeuristicController hammers the synchronous IME API -firstRectForCharacterRange:actualRange: on the main thread (https://crbug.com/446481994#comment41). Given that Chromium needs to synchronously round-trip to a different process to get a response, this means that even on 26.0.1 NSAutoFillHeuristicController causes unacceptable main thread jank. Would love to discuss this further; if you are interested reach out to CH.

Chromium

Ricky Mondello Oct 1, 2025

@avidrissman I did learn some of this late last night, and I’ll be following up. I don’t want to discuss this here, however. :)

@rmondello @siracusa I'm not a developer, there's still a really annoying bug in iOS 26 & iOS 26.0.1 specific to using Apple Podcasts app with Airpods Pro 1 - sound cuts out when the iPhone display turns off. This does not happen with Apple Music or Audible. This does not happen when using the Podcast app connected via Bluetooth to my car. Where would I report this, so it gets to the right people?

John Siracusa Oct 2, 2025

@iestynx I’d suggest starting here: https://www.apple.com/feedback/

If you want to get a person to try to help you solve your problem, then maybe call Apple support on the phone.

Product Feedback

We would love to hear your comments about any of our hardware and software products. Send us your thoughts.

Apple

@[email protected] Has Moved Oct 2, 2025

What's your feel on the UI look and issues that have been reported quite a bit ?

I haven't updated any of my computers yet to Tahoe and I'm waiting