Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

High CPU and memory usage while editing queries

Abierto
#4,216 5 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
30/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
java, typescript, vscode

Línea de trabajo

Comienza reproduciendo el problema con las versiones indicadas de VS Code y la extensión CodeQL, siguiendo los pasos para editar el example.ql generado mientras supervisas el proceso OpenJDK Platform binary. Investiga el issue #594 relacionado y determina qué trabajo continúa después de las ediciones; se considerará terminado cuando se haya identificado la causa y se hayan mejorado el uso de CPU y memoria durante la edición normal.

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

Descripción

bug VSCode

Describe the bug
The performance when just editing queries, not even compiling or running them yet, is not very good. I get high CPU usage (80% for a notebook with 6 cores / 12 processors, running at > 3 GHz), and high memory usage (> 4 GB just by the OpenJDK process of the extension). And this high CPU and memory usage can sometimes even last a few seconds after you made the last edit in the query source code.

It does not even have to be a complex query or query suite, I even get this for the sample "Hello world".
Example:

https://github.com/user-attachments/assets/d5b5cf0c-b6a4-489e-9bfa-18bf3c167a39

Disabling Microsoft Defender Real-time protection did not seem to make a difference.

I know this comparison might not be fair since CodeQL is quite different from lots of other programming languages, but I haven't seen such performance problems with other programming languages or IDEs yet. For example in a Java project in IntelliJ memory usage is about 2 GB, and writing code might trigger some CPU usage spikes up to 40%, but only for a very short time.

Maybe related to #594?

Version
(this is not a new problem, I think I have seen this for a few months already)

VS Code:

Version: 1.106.3 (user setup)
Commit: bf9252a2fb45be6893dd8870c0bf37e2e1766d61
Date: 2025-11-25T22:28:18.024Z
Electron: 37.7.0
ElectronBuildId: 12781156
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

CodeQL extension:

CodeQL extension version: 1.17.6 
CodeQL CLI version: 2.23.6 
Platform: win32 x64

To reproduce

  1. Open a new empty folder in VS Code
  2. Open the Windows Task Manager next to VS Code
  3. Use the command "CodeQL: Create Query"
  4. Select "Java" as language
  5. Edit the generated example.ql, write some arbitrary CodeQL code at fairly decent speed
    ❌ Issue: The extension (more specifically the corresponding "OpenJDK Platform binary" process) shows high CPU and memory usage

Expected behavior
Performance while editing queries should be better

Additional context
Not really sure, and I am really wondering why others have not reported this before.
I don't think there is anything special about my setup, I have no custom CodeQL settings (other than controllerRepo), and as shown above this even occurs for the "Hello world" sample.

Lenguaje dominante
TypeScript
Estrellas
539
Forks
240
Merge medio
2 d 18 h
PR fusionados (30 d)
37

Guía de contribución

Abrir la guía de contribución

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 github/vscode-codeql

Todos los issues de github/vscode-codeql

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.