When I start slaves on Windows or Linux using the Jnlp startup method with the setting "take this slave offline when not needed", the slaves start with low memory usage, but quickly grow their usage up to the point where the slave-node itself goes OOM.

When analyzing I found the following with Eclipse MAT (see below).

This indicates to me that the class JnlpSlaveRestarterInstaller adds a listener, but never removes it.

Thus some related data that is referenced from the JnlpSlaveRestarter is never freed as there are still listeners, even if new restarted were added in the meantime, quickly eating up the available memory on the slave.