microsoft / microsoft/vscode-java-pack

Memory Leak in Linux

Open
#1,543 8 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ai-triaged bug
Dominant language
TypeScript
Stars
352
Forks
166
Avg merge
17h 47m
Merged PRs (30d)
32

Description

After launching the IDE everything fine but as I do changes in my codebase memory consumption keep increasing.
I have installed Java extension package and Spring boot extension pack. Actually I don't know which one is responsible.

Environment:

  • VS Code Version: 1.105.1
  • Extension Version: 0.30.5
  • JDK Type & Version: OpenJDK 17
  • OS Type & Version: Linux

Step to Reproduce:

  1. Open a spring boot project (Larger the code base sooner you will notice)
  2. Start changing in different files
  3. It may take a couple of minute
  4. Monitor the resources

Expected Behavior:
On changing the file overall memory uses should be stable

Actual Behavior:
On each change IDE start checking errors, making auto build and other stuffs. After some times, Java memory reaches to 8GB and keep increasing and system crash or I have to restart vs code to release the memory.

Image

Related Issues:
If you have a large java file like having more than 7K+ lines of code the IDE suggestion are slow, and if you keep working on that file the suggestion will almost stop.

One more Issue I have faced that, on starting the VS code at first the java extension start up but sometimes it sometime (rare) it stuck at java publish diagnosis step. After restart it work

Image

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reproducing the report with VS Code 1.105.1, extension version 0.30.5, OpenJDK 17, Linux, and a larger Spring Boot project while monitoring memory during edits. No source file or test is named; done means identifying the responsible extension or process and confirming that repeated file changes no longer cause unbounded memory growth.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot, vscode
Domain
devtools, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.