Notes from the Google bug tracker linked by the GitHub issue: applying this command to each Chrome/Chromium app impacting your system will workaround the underl

Notes from the Google bug tracker linked by the GitHub issue: applying this command to each Chrome/Chromium app impacting your system will workaround the underlying macOS resource leak (EDIT: which only occurs when Electron mucks with private APIs to fake having native UI): defaults write com.google.Chrome NSAutoFillHeuristicControllerEnabled -bool false https://issues.chromium.org/issues/446481994#comment17 https://issues.chromium.org/issues/446481994#comment17 That command’s equivalent is being patched into Chrome and will have to ripple downward into Electron apps; directing complaints to each electron app impacted with a link to the relevant Google issue workaround will give them sufficient data to mitigate it, if they bother to. Apple is already aware — https://x.com/ian_mcdowell/status/1967326413830472191 https://x.com/ian_mcdowell/status/1967326413830472191 (apologies for the Twitter link, but it’s an Apple employee). EDIT: Someone else has traced the issue to Electron messing with internal OS APIs! Courtesy of https://news.ycombinator.com/item?id=45377253 https://news.ycombinator.com/item?id=45377253 — > It turns out Electron was overriding a private AppKit API (_cornerMask) to apply custom corner masks to vibrant views. ps. This issue was discussed a week ago here: https://news.ycombinator.com/item?id=45292019 https://news.ycombinator.com/item?id=45292019 pps. Manually applying this workaround without scheduling its future removal has a slight but non-zero risk of someday breaking OS-linked autofill in your electron apps in weird or unexpected ways. ppps. I don’t work for anyone, school for another three years minimum.