Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow configuration of VM arguments for LSP process "PropertiesLauncher" #211

Closed
hbrands opened this issue Mar 6, 2019 · 1 comment
Closed
Milestone

Comments

@hbrands
Copy link

hbrands commented Mar 6, 2019

Spring STS 4 seems to launch a separate process called PropertiesLauncher. I guess it's for supporting the Language Server Protocol.

Currently there is no way to pass VM arguments for this process, for example to customize garbage collector and memory settings.

Please provide a way to customize these options.

Reason:
I notice from time to time a slow down which seems to be related to increased garbage collection activity because of a full old generation in the heap. The max heap seems to be limited to 1G.

@martinlippert martinlippert added this to the 4.2.0.RELEASE milestone Mar 12, 2019
@martinlippert
Copy link
Member

martinlippert commented Mar 12, 2019

This got implemented for the 4.2.0 release:

To set specific VM arguments for the language server, please add a specific system property to your eclipse.ini file (or SpringToolSuite4.ini, depending on your install): -Dboot.ls.custom.vmargs

For example, you could add a line like this:

-Dboot.ls.custom.vmargs=-Xmx3G to enable 3G of max heap space for the language server JVM. If you want to set more than one argument, you can add them all at once, for example:

-Dboot.ls.custom.vmargs=-Xmx3048m,-Dsomething=super,-Xdebug,-Xrunjdwp:server=y,transport=dt_socket,address=4000,suspend=n

The individual arguments are comma separated and the value of this property is split into the individual pieces using ,- as the indicator for different arguments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants