redhat-developer / redhat-developer/vscode-java
hot code replace set to auto causes endless "appyling code changes" notifications
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- TypeScript
- Estrellas
- 2.3k
- Forks
- 546
- Merge medio
- 20 h 1 min
- PR fusionados (30 d)
- 11
Descripción
Usually I use the "hode code replace" feature set to auto, so whenever I save the code is automatically injected into the running process. Since a few days this is not working as expected any more.
As soon as I save, the functionality kicks in and the java LSP process goes crazy. It goes up to 200-300% CPU and never comes back.
The problem seems to be that the "Applying code changes ..." functionality is repeatedly started over and over again, but seems to never stop.
It does not recover on its own, I have to restart vscode.
Environment
- Operating System: macOS 11.6.2 (20G314)
- JDK version:openjdk 17.0.1 2021-10-19
- Visual Studio Code version: 1.65.1
- Java extension version: v0.22.0
Steps To Reproduce
- Set "Hot code replace" to
auto - Halt on breakpoint
- Change code and save a few times in a row
After a few times it looks like this:
The log contains proprietary code, so I cannot easily share it here. But it seems fine, no repeating (error) messages of any kind. Just the change detection seems to kick in repeatedly and invoke the "hot code replace" every time (which never returns).
Current Result
"Applying code changes" goes crazy.

Expected Result
Apply codes changes. Java LSP process should permanently consume 200-300% CPU after it.
Additional Informations
If I use the manual "hot code replace" (the lightning symbol), I can't reproduce the issue.
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza reproduciendo el problema con automatic hot code replace, un punto de interrupción y varios guardados; después, inspecciona los puntos de entrada de Java LSP hot-code-replace y de detección de cambios. Compáralo con el flujo manual de lightning-button. Se considera terminado cuando los guardados repetidos aplican los cambios una sola vez, sin notificaciones interminables ni un uso sostenido de CPU del 200–300 %.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java, typescript, vscode
- Área
- developer-experience, tooling
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100