# macOS: accessibility scan can crash Browse when a row is selected

**URL:** <https://forums.ankiweb.net/t/macos-accessibility-scan-can-crash-browse-when-a-row-is-selected/70882>\
**Category:** Development\
**Created:** [August 29, 2026, 10:12pm UTC](https://forums.ankiweb.net/t/macos-accessibility-scan-can-crash-browse-when-a-row-is-selected/70882 "2026-08-29T22:12:51Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![caleblee789](https://avatars.discourse-cdn.com/v4/letter/c/5fc32e/32.png) [@caleblee789](https://forums.ankiweb.net/u/caleblee789)\
**Post date:** [August 29, 2026, 10:12pm UTC](https://forums.ankiweb.net/t/macos-accessibility-scan-can-crash-browse-when-a-row-is-selected/70882/1 "2026-08-29T22:12:52Z")

</div>

I first noticed this while Codex Computer History was monitoring recent  
activity. I opened Anki’s Browse window, and the Anki Browser crashed  
immediately as it appeared. Computer History did not click or edit anything in  
Anki; its SkyComputerUseService process read the macOS accessibility hierarchy.

I later reduced the failure to this reliable route:

1. Start Anki in a fresh disposable profile with sync disabled and no add-ons.
2. Add a Basic card and open Browse, leaving a result row selected.
3. Put Browse in native macOS fullscreen.
4. Ask an authorized accessibility client to capture/read the window hierarchy.

Fullscreen reproduces the route reliably, but selected-card Browse can also  
crash while windowed.

Environment:

- arm64 macOS 26.6.2
- verified crashing application: Anki 26.8.1 with bundled Qt 6.11.0
- controlled Qt 6.11.2 runtime replacement is also affected
- accessibility client: SkyComputerUseService

The crash is EXC\_BAD\_ACCESS / SIGSEGV on Anki’s main thread  
(CrBrowserMain). The raw report’s first relevant frame is an unsymbolicated  
libqcocoa.dylib offset; mapping it against the matching binary resolves it to  
QMacAccessibilityElement accessibilitySelectedChildren. AppKit/HIServices  
hierarchy-copy frames follow. The crash report identifies  
SkyComputerUseService as the querying process.

The most useful controls are:

- fullscreen Browse with no cards and no selection: passes;
- fullscreen Browse with one selected card: crashes;
- reviewer question/answer screens: repeated hierarchy reads and transitions  
pass;
- replacing the complete Qt runtime with 6.11.2 does not fix selected-card  
Browse.

The root cause appears to be a Qt Cocoa ownership regression, not Anki’s review  
code or an add-on. Qt synthesizes native row/cell elements that reuse the parent  
table’s accessibility ID. Cleanup added in Qt commit  
b1ed5f656f064e553b33752f8e87d2f5b9553e38 treats those parent-managed  
placeholders as owners and deletes the table interface when a selected real cell  
replaces one. That invalidates the selected-cell interfaces being returned to  
macOS.

I implemented a narrow upstream Qt candidate: synthesized parent-managed table  
elements no longer delete the parent interface, while real cells continue to  
clean up their own IDs. A native macOS regression test reproduces the table-ID  
deletion on unpatched Qt and passes with the two ownership guards. The complete  
native qaccessibilitymac run passes 11/11.

The candidate was then exercised with exact Anki 26.09b1 application code in a  
fresh sync-disabled, zero-add-on profile. Immediate Browse opening plus the  
first accessibility scan passed, followed by 25 fullscreen reads with one  
selected row, five empty-to-selected model cycles, and 12 fullscreen reads with  
two selected rows. Selected accessibility cells remained exposed and no new  
Anki crash report appeared.

This is not yet a distributable Anki fix. Qt 6.11.2 still contains the defect,  
and no public PyQt runtime wheel currently contains the candidate. The previous  
ID-snapshot experiment is not being proposed because native testing showed it  
could hide selected children while leaving the parent deletion intact.

Related identifiers (direct links omitted because this new forum account is not yet permitted to include them):

- OpenAI Codex issue #41374: the same Qt 6.11 accessibilitySelectedChildren route was observed in Qt Creator under SkyComputerUseService.
- Anki Forums topic #38783: an older Anki Browser/VoiceOver report with a different Qt exception.
- Qt regression commit b1ed5f656f064e553b33752f8e87d2f5b9553e38.
- Qt bug QTBUG-149612.
- Qt Gerrit change 765434.

Qt Gerrit patch set 1 has passed Sanity Review and is awaiting human  
Code-Review.

Would the maintainers like a GitHub development issue to track the upstream Qt  
change and the eventual Anki pyqt6-qt6 runtime update? I will keep any Anki PR  
dependency-only and link the confirmed issue. A spoken VoiceOver announcement  
check remains pending and will be included in packaged-runtime acceptance.

---

<div class="post-metadata">

**Author:** ![abdo](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/abdo/32/654_2.png) [@abdo](https://forums.ankiweb.net/u/abdo)\
**Post date:** [September 24, 2026, 11:39am UTC](https://forums.ankiweb.net/t/macos-accessibility-scan-can-crash-browse-when-a-row-is-selected/70882/2 "2026-09-24T11:39:23Z")

</div>

Thank you. Feel free to create a GitHub issue and we’ll track it.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex002/uploads/anki2/original/1X/8f1279ababc5879d54e4838989f606cfe55af8c7.jpeg) [@system](https://forums.ankiweb.net/u/system)\
**Post date:** [October 24, 2026, 11:40am UTC](https://forums.ankiweb.net/t/macos-accessibility-scan-can-crash-browse-when-a-row-is-selected/70882/3 "2026-10-24T11:40:19Z")

</div>

Closed on October 24, 2026, 11:40am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![Danika\_Dakika](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/danika_dakika/32/17815_2.png) [@Danika\_Dakika](https://forums.ankiweb.net/u/Danika_Dakika)\
**Post date:** [October 28, 2026, 7:30pm UTC](https://forums.ankiweb.net/t/macos-accessibility-scan-can-crash-browse-when-a-row-is-selected/70882/4 "2026-10-28T19:30:53Z")

</div>

Opened on October 28, 2026, 7:30pm UTC



---

<div class="post-metadata">

**Author:** ![aria0moreno](https://avatars.discourse-cdn.com/v4/letter/a/b5e925/32.png) [@aria0moreno](https://forums.ankiweb.net/u/aria0moreno)\
**Post date:** [November 9, 2026, 10:43pm UTC](https://forums.ankiweb.net/t/macos-accessibility-scan-can-crash-browse-when-a-row-is-selected/70882/5 "2026-11-09T22:43:00Z")

</div>

Anki repeatedly crashes when ChatGPT Computer Use attempts to interact with its window.

**Environment**

- Anki 26.9.4, Apple Silicon

- macOS 27.0.1 (26A434)

**Observed behavior**

Reading Anki’s window sometimes succeeds. Opening Browse or interacting with its controls then fails as the window disappears. Subsequent access often shows Anki starting and syncing again.

**Troubleshooting tried**

- Restarted Anki, ChatGPT, and the Mac.

- Confirmed ChatGPT and Codex Computer Use have desktop-control permission.

- Launched Anki using `open -a Anki --args --safemode`; the custom background disappeared, but the failure persisted.

- Tried screenshot-based coordinate clicking; it also failed.

**Crash evidence**

A macOS crash report identifies:

- `EXC_BAD_ACCESS / SIGSEGV`

- Main thread: `CrBrowserMain`

- `libqcocoa.dylib` at offset `554036`

- `NSAccessibilityAttributeAccessorInfo getAttributeValue:forObject:`

- `accessibilityArrayAttributeCount`

- `__AXCopyAttributeValueForHierarchy`

This resembles the reported Qt accessibility defect QTBUG-149612. Is there a compatible fix or supported workaround for Anki 26.9.4?

---

<div class="post-metadata">

**Author:** ![Danika\_Dakika](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/danika_dakika/32/17815_2.png) [@Danika\_Dakika](https://forums.ankiweb.net/u/Danika_Dakika)\
**Post date:** [November 14, 2026, 7:36am UTC](https://forums.ankiweb.net/t/macos-accessibility-scan-can-crash-browse-when-a-row-is-selected/70882/6 "2026-11-14T07:36:36Z")

</div>

> [@aria0moreno](#):
>
> crashes when ChatGPT Computer Use attempts to interact with its window  
> …  
> This resembles the reported Qt accessibility defect QTBUG-149612.

It sounds like you’ve identified the cause and the reason – and they are both outside of Anki’s control.

---

<div class="post-metadata">

**Author:** ![7-11isnotacrime](https://avatars.discourse-cdn.com/v4/letter/7/bc79bd/32.png) [@7-11isnotacrime](https://forums.ankiweb.net/u/7-11isnotacrime)\
**Post date:** [November 17, 2026, 3:46am UTC](https://forums.ankiweb.net/t/macos-accessibility-scan-can-crash-browse-when-a-row-is-selected/70882/7 "2026-11-17T03:46:09Z")

</div>

Could you update Anki’s bundled Qt version to the 6.12.2 version being released tomorrow? The current version has a known macOS accessibility bug (QTBUG-149612) that can cause Anki to crash when other applications access its interface. Bad because third-party screen time trackers may do this.

😃

---

<div class="post-metadata">

**Author:** ![abdo](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/abdo/32/654_2.png) [@abdo](https://forums.ankiweb.net/u/abdo)\
**Post date:** [November 17, 2026, 7:05am UTC](https://forums.ankiweb.net/t/macos-accessibility-scan-can-crash-browse-when-a-row-is-selected/70882/8 "2026-11-17T07:05:29Z")

</div>

I hope we can test Qt 6.12 in the next major release after 26.11.

@Danika_Dakika This thread from the original reporter can be merged here too: [macOS: accessibility scan can crash Browse when a row is selected](https://forums.ankiweb.net/t/macos-accessibility-scan-can-crash-browse-when-a-row-is-selected/70882)
