macOS Computer History intermittently interrupts Logic Pro dragging and fader input via WindowServer/HID stalls

Resolved 💬 1 comment Opened Aug 18, 2026 by Terry-FO Closed Aug 18, 2026
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

Summary

On my Apple Silicon Mac, enabling ChatGPT for macOS "Computer History" causes Logic Pro's continuous mouse/trackpad input to be randomly interrupted. This affects audio-region marquee selection, dragging, and mixer fader movement. Disabling Computer History immediately restores normal behavior.

This appears related to the SkyComputerUseService / Computer Use accessibility and event-monitoring path, and may overlap with #25744 and #29157.

Environment

  • Mac Studio, Apple M1 Max
  • macOS 15.7.1 (24G231)
  • Three-display setup
  • Logic Pro
  • ChatGPT for macOS with Computer History enabled
  • Apple mouse and Magic Trackpad both reproduce the issue

Reproduction

  1. Open Logic Pro and create a new empty project.
  2. Enable ChatGPT for macOS Computer History.
  3. In Logic Pro, marquee-select audio regions, drag regions, or move mixer faders.
  4. The continuous operation is randomly interrupted:
  • the drag may stop almost immediately;
  • sometimes it continues longer;
  • success is highly inconsistent (approximately 1 in 7–8 attempts).
  1. Disable Computer History without rebooting.
  2. Repeat the same operations in Logic Pro: they work normally.
  3. Re-enable Computer History: the problem returns.

The same behavior was reproduced across multiple tests. Fully quitting ChatGPT/Codex and killing its residual processes also temporarily clears the problem, but reopening the app or re-enabling Computer History can reproduce it.

Observed system symptoms

While the problem is active, unified logs contain repeated:

  • SkyComputerUseService AccessibilitySupport.UIElementError messages
  • WindowServer Clearing datagram buffer
  • WindowServer focus/event-monitor and TCC-related delays
  • Logic Pro makeKeyWindow ... returned NO warnings
  • WindowServer run-loop / client-response errors

The system can also become generally laggy: Logic faders become delayed and WindowServer CPU rises. The issue is not limited to one Logic project and is reproduced with both a mouse and trackpad.

Expected behavior

Computer History should coexist with normal high-frequency input in professional applications such as Logic Pro. It should not cause mouseDragged, mouseUp, fader, or keyboard events to be dropped or delayed.

Workarounds

  • Disable Computer History while using Logic Pro.
  • Fully quit ChatGPT/Codex and terminate residual SkyComputerUseService / Codex helper processes if the bad state persists.
  • Restarting macOS is unreliable because the issue can return after the ChatGPT app and its helpers start again.

Requested investigation

  1. Check whether Computer History starts or shares SkyComputerUseService / Computer Use accessibility observers.
  2. Investigate repeated Accessibility UIElement failures and retry loops.
  3. Verify that Computer Use / Computer History helpers are fully reaped after turns and sessions.
  4. Investigate WindowServer TCC event-monitor checks and datagram-buffer clearing during Logic Pro HID activity.
  5. Provide a supported per-app exclusion or a reliable way to disable the Computer Use accessibility/event-monitoring service while keeping ChatGPT available for chat and voice.
  6. Add a regression test for continuous mouse dragging and fader movement in Logic Pro on multi-display Apple Silicon systems.

Related issues:

  • #25744 — helper accumulation causing HID lag and WindowServer/TCC stalls
  • #29157 — leaked SkyComputerUseClient turn-ended helpers

View original on GitHub ↗

1 Comment

github-actions[bot] contributor · 10 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #38562

Powered by Codex Action