I’ve staged binary hotfixes for 1.15.7, 3.4.5, 11.2.0 and 5.5.1 to work around this issue. The workaround is essentially the WoW process doing the same workaround as
defaults write -g NSAutoFillHeuristicControllerEnabled -bool FALSE mentioned above, but should only opt out WoW rather than every app globally.
I’m not 100% sure when the new WoW builds will get deployed but I’m hoping sometime this week or early next week.
Until then, the workaround mentioned above should be fine. The workaround will also be fine to keep after the WoW patches are live.
If for some reason, the workaround mentioned above is causing issues with other apps, you can run:
defaults delete -g NSAutoFillHeuristicControllerEnabled
in Terminal.app to undo it.
15 Likes
It’s worth noting the issue affects all applications that have text input, including other games, even apples own apps like safari and terminal. so even as some app developers apply fix to opt out of feature on their apps, other apps will have slow down until they also opt out (or until apple fixes bug globally in a future update)
as such, I’d keep the global disable in place if you experience slow downs in other apps even after wow hotfix is live.
3 Likes
With this work around, and the fix coming, would you say it is ok to upgrade?
Does running that command to disable the Auto Fill Heuristic Controller also disable permanently passwords auto fill in apps until enabled again?
doesn’t affect that autofill. i’d imagine any autofill features prior to macOS 26 remain unchanged, this is a new autofill feature for macOS 26 and based on name i imagine it’s likely related to apple inteligence auto filling suggested words, so at most maybe you won’t have imessage guess what next word will be? i really don’t know what feature does, just that i don’t miss it cause features I was already using remain unchanged.
3 Likes
ah ok that great thank you very much!! Now that you mention that I have a feeling it’s that apple intelligence thing in messages that puts a little annoying suggestion under the text input bar on occasion. Anyhow greatly appreciate you mate! You a real asset to the Mac community here! Really nice work!
2 Likes
The workaround just got deployed for 11.2.0. I believe 3.4.5 will also get updated today. The rest will likely get updated next Tuesday.
6 Likes
Was just racing here to post that the workaround fix is up. 
Thanks, Rommax!
Has it solved the border issue? I want to know if it’s safe to upgrade to MacOS 26.
The performance degradation issue seems fixed.
WOW’s general performance under os26 is still stutter-ish even while the fps stays looking high. There’s a feeling of lag in its general use. Can’t explain. Like if the client is not making full use of my Apple Silicon.
3.4.5? Y’all got a Wrath-era server laying around and not telling me about it? 
china only. they don’t do cata. and when wrath is over they’re even getting a fun special server that’s vanilla tbc and wrath content all scaled to level 80 so they get the entire classic trilogy experience in a single wrath reboot after regular wrath ends.
Why the hell didn’t we (NA) get this? All I ever hear from folks is that they wish we could have had a choice to stay on Wrath, while progressing forward could continue on a copy or something (like they did from Classic to BC. I kept a copy on Classic and of course, continued to BC. But I still play the Classic one too. Hell I would’ve paid $20 or so like I did during that progression change.). Frankly, many of those same people that had that sentiment as I did, skipped Cata and some are playing MoP ( I did love MoP and played Remix also).
I know I’m rambling, but thank you for explaining what that version meant.
Having this same issue since upgrading to Tahoe, this issue never happened on the previous os. Interesting to see what steps are taken to fix it.
Anyone tried 26.01 which just came out?
Heh. I came here to ask that too.
Does it fix the border issue?
Heaven forbid but are there new problems?
Want to know if it’s safe to upgrade.
since wow worked around issue locally, it’s hared to use wow to test if apple fixed actual bug or not. if they did they left it out of change log.
What about the border issue?
OK … upgraded.
Border issue is still there but you ignore it after a while - should still be fixed though.
Anyone noticing lower performance? I’m able to hold 60fps a lot less with MacOS 26. I’m even dropping to 40s and 50s in remix zones.