# When is 2.1.1 coming out? Reaching a breaking point with this Windows JVM Memory Leak stuff **URL:** \ **Category:** Logstash\ **Created:** [December 4, 2015, 3:07am UTC](https://discuss.elastic.co/t/when-is-2-1-1-coming-out-reaching-a-breaking-point-with-this-windows-jvm-memory-leak-stuff/36338 "2015-12-04T03:07:46Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![h2k](https://avatars.discourse-cdn.com/v4/letter/h/e5b9ba/32.png) [@h2k](https://discuss.elastic.co/u/h2k)\ **Post date:** [December 4, 2015, 3:07am UTC](https://discuss.elastic.co/t/when-is-2-1-1-coming-out-reaching-a-breaking-point-with-this-windows-jvm-memory-leak-stuff/36338/1 "2015-12-04T03:07:46Z")
I am running Logstash 1.5.4 on a number of Windows servers as an agent to collect eventlog and other data. I've done a decent job of tweaking the configuration such that it minimizes the use of expensive filtering and other code, but the memory still blows right past the heap size allocated to the JVM in setup.bat. This is a memory leak -- under normal baseline nothing-happening-on-Windows conditions, the Java process climbs very, very slowly and inexorably toward a wall after which it bombs out (and is restarted by NSSM). Under stress test, the memory climbs much faster, and when the stress test stops, it does not clear the memory. I have seen rumblings that this is due to a memory leak in JRuby, and that there is a fix soon to be available shipped with Logstash 2.1.1. When is that coming out, and in the meantime does anyone have any stopgaps that directly address the memory issue in question? ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [December 4, 2015, 3:53am UTC](https://discuss.elastic.co/t/when-is-2-1-1-coming-out-reaching-a-breaking-point-with-this-windows-jvm-memory-leak-stuff/36338/2 "2015-12-04T03:53:25Z")
I apologize for the inconvenience. We're planning on releasing 2.1.1 early next week. We are doing a lot of integration testing to ensure that the release is good before shipping it. ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [December 4, 2015, 3:53am UTC](https://discuss.elastic.co/t/when-is-2-1-1-coming-out-reaching-a-breaking-point-with-this-windows-jvm-memory-leak-stuff/36338/3 "2015-12-04T03:53:57Z")
> [@h2k](#): > > in the meantime does anyone have any stopgaps that directly address the memory issue in question Unfortunately, no. There are none, other than periodic restarts of Logstash. ---
**Author:** ![h2k](https://avatars.discourse-cdn.com/v4/letter/h/e5b9ba/32.png) [@h2k](https://discuss.elastic.co/u/h2k)\ **Post date:** [December 4, 2015, 4:13am UTC](https://discuss.elastic.co/t/when-is-2-1-1-coming-out-reaching-a-breaking-point-with-this-windows-jvm-memory-leak-stuff/36338/4 "2015-12-04T04:13:44Z")
Early next week sounds good! Is there a notification functionality for releases on the site? ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [December 4, 2015, 5:05am UTC](https://discuss.elastic.co/t/when-is-2-1-1-coming-out-reaching-a-breaking-point-with-this-windows-jvm-memory-leak-stuff/36338/5 "2015-12-04T05:05:13Z")
> [@h2k](#): > > notification functionality Releases will be announced on [elastic.co](http://elastic.co) and here in the forums. ---
**Author:** ![RobT](https://avatars.discourse-cdn.com/v4/letter/r/7ba0ec/32.png) [@RobT](https://discuss.elastic.co/u/RobT)\ **Post date:** [December 7, 2015, 12:52am UTC](https://discuss.elastic.co/t/when-is-2-1-1-coming-out-reaching-a-breaking-point-with-this-windows-jvm-memory-leak-stuff/36338/6 "2015-12-07T00:52:56Z")
Henri, to workaround, I have just been using a simple bat file that will restart the LS and in my case Kibana services in order. Then just setup a scheduled task to call the bat file each night or however often you need it to run. Haven't had any issues with memory since. Robert ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [December 9, 2015, 6:27pm UTC](https://discuss.elastic.co/t/when-is-2-1-1-coming-out-reaching-a-breaking-point-with-this-windows-jvm-memory-leak-stuff/36338/7 "2015-12-09T18:27:58Z")
2.1.1 was released yesterday evening. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 5:19am UTC](https://discuss.elastic.co/t/when-is-2-1-1-coming-out-reaching-a-breaking-point-with-this-windows-jvm-memory-leak-stuff/36338/8 "2017-07-06T05:19:18Z")