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
@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

@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. :)