microsoft / microsoft/vscode-remote-release
When AI conversation logs become excessively lengthy, the entire VS Code application experiences significant sluggishness.
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 469
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
When AI conversation logs become excessively lengthy, the entire Visual Studio Code application experiences severe lag. While using GitHub Copilot Chat, an overly extensive conversation log caused Visual Studio Code's memory usage to reach 2208.6MB and CPU utilisation to climb to 17.5%. The entire window's response time stretched to 10 to 20 seconds, with the terminal freezing and becoming unresponsive. I urge Microsoft to address this issue promptly, as it has been troubling me for quite some time. However, I do not wish to initiate a new AI Chat session.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the slowdown with an excessively lengthy GitHub Copilot Chat conversation while monitoring VS Code memory, CPU, window responsiveness, and terminal behavior. Compare performance before and after the conversation grows; done means the application and terminal remain responsive without requiring a new AI Chat session.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- desktop, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100