Maven spring-boot:run slows down live hover hint significantly. #1743

khe817 · 2020-12-14T17:19:10Z

When I open a Maven Spring Boot project, the Java language server starts up fine, live hover hint works fast (within 20ms - 30ms).
Then I start $ mvn spring-boot:run command in an bash command line window. The language server switches to being very slow with response time for live hover hint around 7000ms:

[Trace - 11:51:59 AM] Sending request 'java/findLinks - (24)'.
Params: {
    "type": "superImplementation",
    "position": {
        "textDocument": {
            "uri": "file:///home/user/.../PublicationIndexController.java"
        },
        "position": {
            "line": 31,
            "character": 13
        }
    }
}

[Trace - 11:52:06 AM] Received response 'java/findLinks - (24)' in 6999ms.
Result: []

Cleaning the Java language server workspace does not fix the issue.

Environment

Operating System: WSL v.2 (Window Subsystem in Linux version 2) version "4.19.128-microsoft-standard" inside "Windows_NT x64 10.0.18363"
JDK version: 11.0.9.1
Visual Studio Code version: 1.52.0
Java extension version: 0.72.0

Steps To Reproduce

Start up a Maven Spring Boot project in VSCode with redhat.java extension enabled. Wait for Java language server to finish starting up. Test live hover hint to see that it works normally.
Open an independent bash command line window (does not matter if it's a terminal inside VSCode or outside VSCode) in WSL. Run command $ mvn spring-boot:run. Wait for Spring Boot to finish starting up.
Try live hover hint in VSCode again. This time, it's very slow.

Additional Informations

While Spring Boot is up and running in the WSL bash command line window. I keep seeing this log recurring in Developer Tool console log window:

Extension Host      workbench.desktop.main.js:5009 Extension Host
Debugger attached.  workbench.desktop.main.js:5009 Debugger attached.

The text was updated successfully, but these errors were encountered:

Eskibear · 2020-12-15T03:28:25Z

Exceptions for using WSL 1 rather than WSL 2
Consider using WSL 1 if:

Your project files must be stored in the Windows file system. WSL 1 offers faster access to files mounted from Windows.
If you will be using your WSL Linux distribution to access project files on the Windows file system, and these files cannot be stored on the Linux file system, you will achieve faster performance across the OS files systems by using WSL 1.

A project which requires cross-compilation using both Windows and Linux tools on the same files.
File performance across the Windows and Linux operating systems is faster in WSL 1 than WSL 2, so if you are using Windows applications to access Linux files, you will currently achieve faster performance with WSL 1.

See https://docs.microsoft.com/en-us/windows/wsl/compare-versions#exceptions-for-using-wsl-1-rather-than-wsl-2
What if you run mvn spring-boot:run in WSL 1 or Windows itself (e.g. CMD)?

BTW, Remote WSL is how VS Code recommends for WSL scenarios.

khe817 · 2020-12-15T03:46:58Z

Thank you for replying!

I am aware of the issue with slow access in windows file system with wsl2. My project folders are all under linux file system. I open and run my projects under remote wsl extension as recommended already. I believe I have everything runs under wsl2, no cross platform of any kinds that I know of. So I don't think it's the issue with accessing windows file system under wsl2.

This issue happened after I upgraded to the newest vscode version last Friday. Everything worked fine before that. I tried to install previous versions of redhat.java with no improvement.

Any helps will be very much appreciated!

Eskibear · 2020-12-15T06:39:19Z

I somehow managed to reproduce it in WSL.

CPU: Xeon E5-1620 v4 @ 3.50GHz, 4 cores
RAM: 32GB
OS: Windows 10, Build 19042
VS Code: 1.52.0
Remote WSL Extension: 0.52.0
JDK in WSL: openjdk-11-jdk installed via apt-get
Extensions intalled in WSL: Java Extension Pack
Java Extension: 0.72.0
Sample project: spring-petclinic

At first, it was WSL 1 (although I set default WSL version to 2, it turned out vscode launched version 1).
In my case, after run mvn spring-boot: run in an external WSL terminal, I could feel hovering become slightly slower for some symbols, but still working. When I hovered on type Collection in OwnerController.java#L91, for the fisrt time, it stuck on "Loading...". After retrying hovering for several times, it went back to normal.

Checking the LS log, I find:

[Error - 1:47:35 PM] Dec 15, 2020, 1:47:35 PM Timed out while retrieving the attached javadoc for Collection {key=Ljava/util/Collection<Lorg/springframework/samples/petclinic/owner/Owner;>;} [in Collection.class [in java.util [in <module:java.base>]]] 
Timed out while retrieving the attached javadoc for Collection {key=Ljava/util/Collection<Lorg/springframework/samples/petclinic/owner/Owner;>;} [in Collection.class [in java.util [in <module:java.base>]]] 
Java Model Exception: Java Model Status [Timed out while retrieving the attached javadoc for Collection {key=Ljava/util/Collection<Lorg/springframework/samples/petclinic/owner/Owner;>;} [in Collection.class [in java.util [in <module:java.base>]]] ]
	at org.eclipse.jdt.internal.core.JavaElement.getURLContents(JavaElement.java:931)
	at org.eclipse.jdt.internal.core.BinaryType.getJavadocContents(BinaryType.java:1088)
	at org.eclipse.jdt.internal.core.BinaryType.getAttachedJavadoc(BinaryType.java:1046)
	at org.eclipse.jdt.ls.core.internal.javadoc.JavadocContentAccess2.getHTMLContent(JavadocContentAccess2.java:595)
	at org.eclipse.jdt.ls.core.internal.javadoc.JavadocContentAccess2.getMarkdownContentReader(JavadocContentAccess2.java:2506)
	at org.eclipse.jdt.ls.core.internal.HoverInfoProvider.computeJavadoc(HoverInfoProvider.java:273)
	at org.eclipse.jdt.ls.core.internal.HoverInfoProvider.computeHover(HoverInfoProvider.java:145)
	at org.eclipse.jdt.ls.core.internal.handlers.HoverHandler.computeHover(HoverHandler.java:52)
	at org.eclipse.jdt.ls.core.internal.handlers.HoverHandler.hover(HoverHandler.java:41)
	at org.eclipse.jdt.ls.core.internal.handlers.JDTLanguageServer.lambda$6(JDTLanguageServer.java:552)
	at org.eclipse.jdt.ls.core.internal.BaseJDTLanguageServer.lambda$0(BaseJDTLanguageServer.java:75)
	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:642)
	at java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)
	at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183)

Later I switched it to WSL 2 using below commands.

C:\Users\username>wsl -l -v
  NAME            STATE           VERSION
* Ubuntu-18.04    Running         1

C:\Users\username>wsl --set-version Ubuntu-18.04 2
Conversion in progress, this may take a few minutes...
For information on key differences with WSL 2 please visit https://aka.ms/wsl2
Conversion complete.

C:\Users\username>wsl -l -v
  NAME            STATE           VERSION
* Ubuntu-18.04    Stopped         2

And I find it doesn't matter whether I run mvn spring-boot: run or not, the issue just randomly occured when I hover on some symbols for the first time.

arguser · 2020-12-15T13:37:18Z

Hello @khe817, I'm experiencing something similar since Friday. I'm not sure if this is related to the Docker Desktop update or the VSCode/VSCode Extension update which also been around Friday. Do you experience slow code navigation and step debugging?

khe817 · 2020-12-15T14:17:10Z

@arguser, I experience slow code navigation and step debugging too. Basically, running mvn spring-boot: run somehow slows the Java language server down significantly, which didn't happen before.

Update: Running mvn spring-boot: run slows down TS/JS language server too. I think at this point, it's an issue with VSCode itself, not just redhat.java extension.

arguser · 2020-12-15T17:29:03Z

@khe817 I'm trying the previous VSCode version: 1.51.1, going to report back if this work better.

UPDATE: It does definitely work better, go download https://code.visualstudio.com/updates/v1_51

shanewaz-abbas · 2020-12-18T19:51:42Z

I am running into the same issue with a spring app. This app is running in remote host using ssh. As soon as I start the debugger everything becomes super slow. Downgrading vscode solves the issue.
This is the result of running top inside the ssh host:

> top
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                                                                                                          
 2612 xxxxxxx+  20   0 1498564 163416  34016 R 100.0  0.5  14:53.38 node

> ps -p 2612 -o args
/home/xxxxxx/.vscode-server/bin/ea3859d4ba2f3e577a159bc91e3074c5d85c0523/node /home/xxxxxx/.vscode-server/bin/ea3859d4ba2f3e577a159bc91e3074c5d85c0523/out/bootstrap-fork --type=extensionHost --uriTransformerPath=/home/xxxxxx/.vscode-server/bin/ea3859d4ba2f3e577a159bc91e3074c5d85c0523/out/vs/server/uriTransformer.js

alexdima · 2020-12-18T21:59:13Z

This might be caused by vscode's new automatic port forwarding feature which scans the remote OS for available ports in order to forward them locally (microsoft/vscode#112843)

khe817 · 2021-02-04T19:30:54Z

The issue has been fixed in the newest version of VSCode 1.53.0.

shanewaz-abbas · 2021-02-05T22:13:04Z

Issue still happening for me. Unfortunately.

khe817 changed the title ~~Maven spring-boot:run slows down Java language server's live hover hint significantly.~~ Maven spring-boot:run slows down live hover hint significantly. Dec 14, 2020

testforstephen added the performance label Dec 15, 2020

khe817 mentioned this issue Dec 15, 2020

Maven spring-boot:run slows down Java and TS/JS language servers microsoft/vscode#112581

Closed

testforstephen assigned Eskibear Dec 17, 2020

shanewaz-abbas mentioned this issue Dec 18, 2020

Extention host consume 100% of the cpu microsoft/vscode#112466

Closed

alexdima mentioned this issue Dec 18, 2020

Port scanning executes even if auto forward ports is off microsoft/vscode#112843

Closed

khe817 closed this as completed Feb 4, 2021

snyk-bot mentioned this issue Apr 7, 2022

[Snyk] Security upgrade winston from 3.2.1 to 3.3.0 Manny27nyc/vscode-java#7

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Maven spring-boot:run slows down live hover hint significantly. #1743

Maven spring-boot:run slows down live hover hint significantly. #1743

khe817 commented Dec 14, 2020 •

edited

Loading

Eskibear commented Dec 15, 2020

khe817 commented Dec 15, 2020

Eskibear commented Dec 15, 2020

arguser commented Dec 15, 2020

khe817 commented Dec 15, 2020 •

edited

Loading

arguser commented Dec 15, 2020 •

edited

Loading

shanewaz-abbas commented Dec 18, 2020 •

edited

Loading

alexdima commented Dec 18, 2020

khe817 commented Feb 4, 2021

shanewaz-abbas commented Feb 5, 2021

Maven spring-boot:run slows down live hover hint significantly. #1743

Maven spring-boot:run slows down live hover hint significantly. #1743

Comments

khe817 commented Dec 14, 2020 • edited Loading

Environment

Steps To Reproduce

Additional Informations

Eskibear commented Dec 15, 2020

khe817 commented Dec 15, 2020

Eskibear commented Dec 15, 2020

arguser commented Dec 15, 2020

khe817 commented Dec 15, 2020 • edited Loading

arguser commented Dec 15, 2020 • edited Loading

shanewaz-abbas commented Dec 18, 2020 • edited Loading

alexdima commented Dec 18, 2020

khe817 commented Feb 4, 2021

shanewaz-abbas commented Feb 5, 2021

khe817 commented Dec 14, 2020 •

edited

Loading

khe817 commented Dec 15, 2020 •

edited

Loading

arguser commented Dec 15, 2020 •

edited

Loading

shanewaz-abbas commented Dec 18, 2020 •

edited

Loading