Memory Leak in Linux
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- java, spring-boot, vscode
- Domain
- devtools, performance
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.
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:
- Open a spring boot project (Larger the code base sooner you will notice)
- Start changing in different files
- It may take a couple of minute
- 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.
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
- Dominant language
- TypeScript
- Stars
- 352
- Forks
- 166
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 32
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/vscode-java-pack
-
ai-triaged bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/vscode-java-pack#1443 · 1 comment · 2 reactions ·
-
ai-triaged bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
microsoft/vscode-java-pack#1425 · 1 comment ·
-
ai-triaged enhancement feature-request
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoft/vscode-java-pack#1423 · 2 comments · 1 reaction ·
-
ai-triaged area/jdtls bug needs-investigation
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/vscode-java-pack#1420 · 1 comment ·
-
java.project.sourcePaths Setting Fails to Exclude Test Directory from References and Call Hierarchy Openai-triaged bug language-server
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/vscode-java-pack#1408 · 1 comment ·
All issues in microsoft/vscode-java-pack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/claude-code#96687 ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
AOSSIE-Org/DebateAI#582 · 2 comments ·