Roman Marchenko

Results 36 comments of Roman Marchenko

I'm still facing the issue with `redhat.java-1.30.0` on VSCode 1.89

Still there with VSCode 1.89.1 and redhat.java-1.31.0-linux-x64 on JDK17 sources.

Using version 1.32 now, I uninstalled the extensions, and install it again, the issue seems still there for me. Also tried this setting in my workspace: `"java.compile.nullAnalysis.mode": "disabled"` it doesn't...

I've cleaned workspace directory in both Windows and WSL. Removed ".vscode*" folders from $HOME and from the project directory. The issue still occurs. Logs attached, [vscode.log](https://github.com/user-attachments/files/16111681/vscode.log) @snjeza Did you try...

> Could you reproduce the issue outside of WSL? Yes, I'm able to reproduce it on Windows 11: ![image](https://github.com/redhat-developer/vscode-java/assets/17044077/3768fa07-a5fb-4691-9a9a-6c4b41597d2c) ![image](https://github.com/redhat-developer/vscode-java/assets/17044077/3bcff6ae-ddd4-47dd-9b2b-05f5f285d7b2) ![image](https://github.com/redhat-developer/vscode-java/assets/17044077/c6441a1c-dd67-4896-b863-aafb17fba3f7) All of the tries above ended up with OOM...

For the following settings, the try ended up with OOM error on Windows 11: ``` { "java.jdt.ls.vmargs": "-XX:+UseParallelGC -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 -Dsun.zip.disableMemoryMapping=true -Xmx4G -Xms100m -Xlog:disable", "java.trace.server": "verbose" } ``` The logs:...

@snjeza User settings: [settings.json](https://github.com/user-attachments/files/16328388/settings.json) Workspace setting: [settings.json](https://github.com/user-attachments/files/16202541/settings.json)

@snjeza Here are the results: - [`"java.import.maven.enabled": true`](https://github.com/redhat-developer/vscode-java/issues/3387#issuecomment-2226941933) - issue is **NOT** reproducible - [`"java.import.maven.enabled": false` + `"java.project.sourcePaths"`](https://github.com/redhat-developer/vscode-java/issues/3387#issuecomment-2226994017) - issue is **NOT** reproducible Double checked **without the changes above** -...

@snjeza I'm happy to use the setting above as a workaround, however I don't like an idea to tune settings for all new workspaces I create. Is it going to...

@snjeza The issue is still reproducible on Windows 11 with "**test**" folder rather than "**src**": ``` "java.import.maven.enabled": false, "java.project.sourcePaths": [ "test" ] ``` And it is still reproducible on WSL...