https://community.splunk.com/t5/Getting-Data-In/The-executable-splunk-regmon-exe-just-keeps-eating-up-more-and/m-p/31851#M5601 <P>I had to “End Process” when it had used 1.2G of my RAM.</P> <P>I am running version 5.0 ...</P> <P>Something configured incorrectly?</P> Tue, 13 Nov 2012 01:47:48 GMT HBrunnings 2012-11-13T01:47:48Z https://community.splunk.com/t5/Getting-Data-In/The-executable-splunk-regmon-exe-just-keeps-eating-up-more-and/m-p/31851#M5601 <P>I had to “End Process” when it had used 1.2G of my RAM.</P> <P>I am running version 5.0 ...</P> <P>Something configured incorrectly?</P> Tue, 13 Nov 2012 01:47:48 GMT https://community.splunk.com/t5/Getting-Data-In/The-executable-splunk-regmon-exe-just-keeps-eating-up-more-and/m-p/31851#M5601 HBrunnings 2012-11-13T01:47:48Z https://community.splunk.com/t5/Getting-Data-In/The-executable-splunk-regmon-exe-just-keeps-eating-up-more-and/m-p/31852#M5602 <P>I know there's a known bug in 5.0 where the process splunkd.exe eats ram if receiving large amounts of UDP traffic.</P> <P>"We have determined that in Splunk 5.0, active UDP inputs cause the main splunkd process to leak memory. The rate of this memory leak appears to be proportional to the rate of data that is being received on the UDP input(s). For that reason, it is possible for a very active UDP input to cause splunkd to eventually exhaust all available memory on the host.<BR /> The bug that references this behavior is SPL-58075 and has been added to the list of known issues for Splunk 5.0.<BR /> We are actively working towards the release of a fix to this issue in the next few days."</P> Tue, 13 Nov 2012 15:47:49 GMT https://community.splunk.com/t5/Getting-Data-In/The-executable-splunk-regmon-exe-just-keeps-eating-up-more-and/m-p/31852#M5602 larryrosen 2012-11-13T15:47:49Z