Anki repeatedly crashes during screen-sharing/computer-control interaction on my Mac, including a session with ChatGPT. The exact minimal trigger has not been isolated.
Environment:
Anki 26.9.2
macOS 26.6.2 (25G83), Apple Silicon
Qt 6.11.0 / PyQt 6.11.0
Enabled add-ons: SynapsePro and Interactive Heatmap
Five crash reports from September 29–30 show the same pattern:
EXC_BAD_ACCESS / SIGSEGV
Triggered thread: CrBrowserMain / main thread
libqcocoa.dylib followed by NSAccessibilityAttributeAccessorInfo, accessibilityArrayAttributeCount, and __AXCopyAttributeValueForHierarchy
I’ve attached an extracted crash report with the stack and binary identifiers. I have not yet tested with add-ons disabled.
Could someone help determine whether this is a Qt accessibility issue or an add-on interaction but The forum prevents new users from attaching files, so here is the relevant crash-stack excerpt:
The same pattern appears in five crash reports from September 29–30. I can provide the complete report if attachment permissions are enabled or another upload method is available.
Another affected installation with the same libqcocoa.dylib + 554036 / accessibility stack reported above: Anki quits every time I open Browse, preventing card management and moving newly imported cards into existing decks.
Steps to reproduce (my normal workflow)
Start Anki with my existing profile/collection.
Click Browse in the main window.
Anki exits instead of leaving Browse usable.
Verified environment
Anki/aqt 26.9.3 (26.09.3), matching the installed metadata and macOS crash reports.
macOS 26.3 (25D125), native Apple Silicon / arm64.
Bundled Qt 6.11.2, PyQt6 6.11.0, Python 3.13.15.
The standard Anki2/addons21 folder contains no add-on directories. A separate safe-mode reproduction is still pending: the diagnostic UI tool could not target this Anki app. An empty add-ons folder is not being presented as a safe-mode test.
Already tried, without success
Reset window sizes in Preferences.
Changed the video driver from Metal to Software.
Restarted Anki after the settings changes.
The current gldriver6 file contains “software”.
Crash evidence
Seven macOS reports from this incident on 28 October 2026 show the same Qt Cocoa/accessibility stack on thread 0 (CrBrowserMain / com.apple.main-thread). Six report EXC_BAD_ACCESS / SIGSEGV; one reports EXC_BAD_ACCESS / SIGBUS. The Qt frame is unsymbolicated: libqcocoa.dylib + 554036 in the six SIGSEGV reports and + 553996 in the SIGBUS report.
Sanitized excerpt from the latest report, after Python signal-handler frames:
Codex Computer Use (SkyComputerUseService) and Wispr Flow were running during investigation. No Lasso, BetterTouchTool, Rectangle or Magnet process was found in the process-name check. These crash reports do not identify the querying client, so neither running application is established as the trigger. An accessibility-readers-disabled comparison and QT_ACCESSIBILITY=0 remain untested.
This resembles topic #70882. I also checked #70330; its cloze-highlighting add-on workaround is not assumed applicable here. GitHub ankitects/anki #5800 is closed without comments; that alone does not demonstrate a fix.
The official QTBUG-149612 is now Closed/Fixed and links merged Qt change 772484. Fix versions 6.12.1, 6.13.0 and 6.8.10 are all still listed as unreleased as of 28 October.
Does my crash fit that upstream defect? Is a compatible packaged Anki fix planned, or is there a reliable interim workaround? Which targeted diagnostic would help next? I can provide further sanitized evidence while avoiding collection resets or changes to cards/review history.