Copilot breaks backspace on VSCode, macOS

[d3v-null]

Select Topic Area

Bug

Body

Hi,
I've just started paying for a GitHub Copilot subscription, so let me know if there's a different support I should be using.

in VSCode, while editing basically any file, the functionality of my backspace key will stop working randomly. I can type other keys, just not backspace. There's nothing wrong with my keyboard.

When it happens, I see a spinning circle in the status bar, and everything related to Copilot is frozen. Any Copilot commands I submit from the command palette do nothing.

I see nothing useful in the Output tab under GitHub Copilot, Chat or Log, or Developer Console around the time it stops working.

The backspace functionality returns when I disable the GitHub Copilot extension.

Anecdotally I have to do this every few minutes, and it seems to happen more often when I have an ipython notebook open within a rust workspace. I've tried moving from a multi-directory workspace to a single directory and no lock.

it happens in vscode remote too.

Hardware version info

  Model Name:	MacBook Pro
  Model Identifier:	Mac14,6
  Model Number:	MNXA3X/A
  Chip:	Apple M2 Max
  Total Number of Cores:	12 (8 performance and 4 efficiency)
  Memory:	64 GB
  System Version:	macOS 15.1 (24B83)

GitHub Copilot extension version v1.243.0

VSCode version info

Version: 1.95.1
Commit: 65edc4939843c90c34d61f4ce11704f09d3e5cb6
Date: 2024-10-31T05:14:54.222Z (4 days ago)
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.1.0

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐