Frequent UI Freezes (Beach Ball) during Agent Chat sessions on M4 Mac

Open
#812 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
macos, swift

Research direction

The report names no source file or test. First reproduce a prolonged Agent Chat session on macOS 26.4, Xcode 26.4, and CopilotForXcode v0.47.0, then inspect the application state when the beach ball appears, including main-thread and memory behavior. Done means identifying the cause and verifying that the UI no longer freezes, with a regression check if applicable.

Written by the indexing model from the issue text.

Description

reviewed

Description
I am experiencing frequent application hangs (spinning wait cursor/beach ball) when using the Agent Chat feature in CopilotForXcode. After a period of active use, the interface becomes unresponsive, necessitating a restart of Xcode to restore functionality.

Environment
Hardware: MacBook Air M4

Memory: 16GB RAM

macOS Version: [macOS 26.4]

Xcode Version: [Xcode 26.4]

CopilotForXcode Version: [v0.47.0]

Steps to Reproduce
Open Xcode and initiate a session with CopilotForXcode.

Engage in a prolonged conversation or multiple successive queries within the Agent Chat.

After some time, the UI freezes, and the "beach ball" appears.

Chat Window remains unresponsive for long time.

Observations
The issue seems to trigger more frequently during long chat histories.

System memory pressure appears manageable, but the communication between the agent and Xcode seems to dead-lock the main thread.

Restarting Xcode is currently the only workaround.

Additional Context
I am looking for advice on whether this is a known memory leak or a threading issue, and if there are any specific settings (e.g., chat history limits or model configurations) that can mitigate this behavior on 16GB RAM systems.

Dominant language
Swift
Stars
6.3k
Forks
2k
Avg merge
3d 21h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/CopilotForXcode

All issues in github/CopilotForXcode

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.