[macOS][Computer Use] Accessibility traversal freezes DataGrip result grids and drives CPU to 100%

What version of the Codex App are you using (From “About Codex” dialog)?

26.831.20005 (build 7524)

What subscription do you have?

Personal ChatGPT account (ChatGPT Pro 5X)

What platform is your computer?

Darwin 25.6.0 arm64 arm (macOS 26.6.2, build 25G83)

What issue are you seeing?

This is a duplicate of #40305 and is related to #38873, filed with additional runtime evidence from a separate machine.

When Codex Computer Use reads the active DataGrip window containing a non-trivial SQL result grid, DataGrip becomes unresponsive. The DataGrip process rises from approximately 0.2% CPU to 98–102% and the accessibility read can take more than two minutes.

Disabling macOS Accessibility access for ChatGPT / Codex Computer Use, or quitting the ChatGPT app, prevents the freeze.

DataGrip's idea.log recorded 202 repeated exceptions in one burst:

java.lang.ArrayIndexOutOfBoundsException: 5 >= 4
    at java.util.Vector.elementAt(Vector.java:466)
    at javax.swing.table.DefaultTableColumnModel.getColumn(DefaultTableColumnModel.java:298)
    at com.intellij.database.run.ui.table.TableResultView$MyTableColumnModel.getColumn(TableResultView.java:1162)
    at com.intellij.database.run.ui.table.TableResultView.getValueAt(TableResultView.java:1693)
    at com.intellij.ui.table.JBTable$AccessibleJBTable$AccessibleJBTableCell.getCurrentComponent(JBTable.java:1566)
    at sun.lwawt.macosx.CAccessibility.getChildrenAndRolesImpl(CAccessibility.java:708)

During the freeze:

• Java EDT: WAITING in java.awt.EventQueue.getNextEvent
• Native AppKit/AWT loop: busy in LWCToolkit_doAWTRunLoopImpl, CFRunLoopDoBlocks, and CFSetContainsValue
• DataGrip heap: approximately 293–380 MB used out of a 2 GB maximum
• System memory and disk pressure: normal
• JDBC helper: idle

This points to accessibility-tree traversal of a mutable JetBrains JTable, rather than JDBC execution, indexing, GC, or system resource exhaustion.

What steps can reproduce the bug?

1. Enable ChatGPT and Codex Computer Use under macOS System Settings > Privacy & Security > Accessibility and Screen & System Audio Recording.
2. Launch DataGrip 2026.2.4 with JetBrains Runtime 25.0.4+1-b508.27.
3. Open a SQL result grid containing hundreds or more rows.
4. Ask Codex Computer Use to inspect/read the active DataGrip window.
5. Observe that DataGrip becomes unresponsive and its CPU usage approaches 100%.
6. Quit ChatGPT or disable its Accessibility permission.
7. Repeat the same DataGrip operation and observe that the freeze no longer occurs.

What is the expected behavior?

Codex Computer Use should inspect only the visible or otherwise bounded portion of a large virtualized table. Accessibility traversal should be cancellable and must not block or saturate the target application's native UI event loop.

Additional information

Related reports:

• #40305
• #38873
• JetBrains Runtime JBR-10147: a related macOS accessibility freeze while updating a large JTree

Possible Codex-side mitigation:

• Limit accessibility traversal by node count, depth, and elapsed time.
• Read only visible rows/cells from virtualized tables.
• Cancel in-flight traversal when the request finishes or permissions are disabled.
• Avoid recursively enumerating all accessibility children of JetBrains result grids.

Start by tracing the Codex Computer Use accessibility traversal on macOS, then reproduce against a DataGrip result grid with hundreds of rows using the listed steps. Compare traversal behavior with Accessibility permission disabled. Done means large virtualized tables are bounded or cancellable without freezing the target app or driving CPU near 100%.