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

Abierto
#13,437 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 8 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
typescript, vscode

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
TypeScript
Estrellas
36.5k
Forks
5.6k
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de continuedev/continue

Todos los issues de continuedev/continue

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.