VS Code + Continue Freezing and Showing “Not Responding” – Possible Issue Beyond Resource Usage

Open
#13,437 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 8 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
typescript, vscode

Research direction

Start by reviewing the Continue extension logs and VS Code’s extension host diagnostics for the reported freezing on Ubuntu 24.04.5 with Continue 2.0.0; the issue does not identify a file, reproduction steps, or logs. Done would mean identifying a reproducible cause and documenting or fixing it, but the report needs more diagnostic details before work can be scoped.

Written by the indexing model from the issue text.

Description

Before submitting your bug report
Relevant environment info
- OS: Ubuntu 24.04.5 LTS
- Continue version: 2.0.0
- IDE version: 1.143.1
- Model: any
- config:
  

  
  OR link to agent in Continue hub:
Description

I'm having an issue with VS Code + Continue. I have a 13th-generation Intel Core i7 processor, 23 GB of RAM, and an SSD, but I keep seeing this warning pop up frequently.

https://docs.accuhealth.cl/vscode.png

Sometimes VS Code also crashes. When it does, I think memory usage goes up to around 22–23 GB.

I previously had VS Code installed via Snap, but I recently downloaded and installed the .deb package from the official website. I think this has improved things a little.

Is anyone else experiencing the same issue?

consumo (htop)
https://docs.accuhealth.cl/htop.png

The fact that VS Code shows the “Not Responding” message doesn't necessarily mean it's caused by high resource usage on my computer. I have a feeling something else is going on.

To reproduce

No response

Log output

Dominant language
TypeScript
Stars
36.5k
Forks
5.6k
PR merge metrics
No merged PRs in 30d

Getting set up

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 continuedev/continue

All issues in continuedev/continue

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.