You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The language server is configured to run with 1GB of heap by default. Depending on your use case, you might be able to reduce that size by overriding the Xmx1G value in the java.jdt.ls.vmargs preference, to say Xmx512m. Be aware this might make the Java server much slower, unresponsive or crash as it could run out of memory.
Looks like this was more of a question/call for performance improvement that had an acceptable workaround for then.
In #1262 we did improve performance by encouraging the language server to perform garbage collection more frequently. This would have especially improved cases where initial project import consumed a lot of memory, and freed it very relucantly, leading to the OOM issues.
Also, we're looking at catching, reporting, and handling OOM issues more gracefully on #1959 .
Activity
fbricon commentedon Oct 21, 2019
The language server is configured to run with 1GB of heap by default. Depending on your use case, you might be able to reduce that size by overriding the
Xmx1Gvalue in thejava.jdt.ls.vmargspreference, to sayXmx512m. Be aware this might make the Java server much slower, unresponsive or crash as it could run out of memory.rgrunber commentedon Jul 7, 2021
Looks like this was more of a question/call for performance improvement that had an acceptable workaround for then.
In #1262 we did improve performance by encouraging the language server to perform garbage collection more frequently. This would have especially improved cases where initial project import consumed a lot of memory, and freed it very relucantly, leading to the OOM issues.
Also, we're looking at catching, reporting, and handling OOM issues more gracefully on #1959 .
Marking this as a duplicate of that for now.