LS 2.0 & Java Memory Leak


Can someone please confirm whether or not the latest LS 2.1 release fixes the Java memory leak issue described here:

Since deploying LS 2.0 to a number of Windows machines I have been seeing the java.exe process regularly exceeding 2GB memory (private working set). This is crippling our expansion of the ELK stack into our infrastructure. We do use file/folder globbing in our paths...

Does 2.1 fix this?


Does not look like it is: