VSCode Copilot Completely Unusable with Freezes Since Latest Update #179712
Replies: 6 comments 5 replies
-
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
BetaWas this translation helpful?Give feedback.
-
Genuinely surprised by how awful this is. Since my post, I've had 8 more crashes. That's nearly once every 7 minutes. Literally since the update this morning. Extremely disappointed. |
BetaWas this translation helpful?Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Freezing appears during the status in the statusbar: |
BetaWas this translation helpful?Give feedback.
-
I have the same issue. VSCode work find til I open a github copilot chat, the log from terminal still running but cannot interact with VSCode at all and have to close it via task manager |
BetaWas this translation helpful?Give feedback.
-
Same situation here. Please, fix it. I just updated VS Code to the latest version and it is completely unusable. Windows 11. I am in the middle of important project with really long conversations in Copilot Chat (agent mode) and it just frezes every few minutes. Yes, the IDE seems to be somehow running since eg. the text cursor is stil blinking and copilot continues to output text for some time. However, except of that, VS Code is in complete freeze. |
BetaWas this translation helpful?Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Since yesterday, I have potentially quite important observation: It happens for me only when I switch windows. a) When I am working only inside of VSC, it is without any issue for hours (without mentioned freeze). Update: Aditional info - it happens also when I am using VSC over Win remote (RDP) and I just minimalize the window with the RDP client on the Host computer for some time when the Copilot is active and doing something. |
BetaWas this translation helpful?Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Copilot Feature Area
Copilot Agent Mode
Body
Hi,
I am writing due to the fact that after updating VSCode to the latest version just 12 hours ago, I have faced 20+ hangs while using GitHub Copilot - just as the Agent is completing a request (even if no code was changed). They have unfortunately been getting more and more frequent, to the point I can't send a single request to Copilot.
I have never faced this issue, and have been using GitHub Copilot for many months. Unfortunately, VSCode updated automatically on restart this morning, otherwise I would have never gone ahead with the update. This update is quite literally rendering Copilot completely useless.
System Details:
Dell Latitude 5421 Laptop
Intel i5-11500H
16GB DDR4 RAM
256GB SSD
Windows 11 Pro 24H2
No third-party antivirus.
Windows Defender disabled.
Working on the exact same project as I was working on before the update and the crashes.
Things Noticed:
Crash ONLY occurs at the end of a request (not every request, but a decent amount). No discernible rhythm or pattern to it - happens whether the Agent makes changes to the code or not, happens whether the code is running or not.
Code: localhost API and app, one terminal with Python 3.11.x with FastAPI, one terminal with a NextJS web app (though even if nothing is running, the crash occurs - even on a fresh laptop restart, the crash sometimes occurs on the first request).
No CPU/disk/RAM spikes during this.
Visually, I am able to SEE the rest of VSCode work fine - terminals outputting logs perfectly, application still running on localhost. However, completely unable to interact with VSCode at all. Unable to close it too, except through force quit via Task Manager.
Only pattern I noticed is this:
EDIT: Unfortunately, the above pattern does not seem to hold in ALL cases, although for a majority of cases I faced, it was the case. Right after writing this post, I had a VSCode freeze but Copilot's full response did NOT disappear on relaunch.
Please let me know what else you would require from me! Looking for an answer as soon as possible, as VSCode has become completely unusable, and this has been bothering me for 12 hours; the only relevant thread I saw was from 8 months ago, and I wonder if it is the same bug still affecting Copilot users. If so, that would be extremely, extremely disappointing.
Kind regards,
A
BetaWas this translation helpful?Give feedback.
All reactions