[checkmk-commits] 4718 FIX Fixed memory leak in Check_MK check helpers when started in verbose mode

Module: check_mk Branch: master Commit: 8fa77febaeacc4142264e2fa5a80ec575c817c85 URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=8fa77febaeacc4… Author: Lars Michelsen <lm(a)mathias-kettner.de> Date: Tue May 16 13:57:44 2017 +0200 4718 FIX Fixed memory leak in Check_MK check helpers when started in verbose mode When the Check_MK helpers are configured with a higher log level than the default Notice log level the Check_MK helpers were leaking memory. This can be configured by changing the option "Check_MK check helpers" of the global setting "Logging of the core" to e.g. Informational. In this mode the helper gathers information about some changed variables during runtime and the memory usage. It also allows to debug different mechanics of the helpers. If you enabled this, each reload of the core (not restart) was triggering the memory leak in the helpers. In extreme situations this could lead to duplication of the memory usage on each reload. Change-Id: I561abfdffd2f10d88a277d2c3267915a68e8ab7c --- .werks/4718 | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/.werks/4718 b/.werks/4718 new file mode 100644 index 0000000..4025c3a --- /dev/null +++ b/.werks/4718 @@ -0,0 +1,20 @@ +Title: Fixed memory leak in Check_MK check helpers when started in verbose mode +Level: 2 +Component: core +Compatible: compat +Edition: cee +Version: 1.5.0i1 +Date: 1494935598 +Class: fix + +When the Check_MK helpers are configured with a higher log level than the default +Notice log level the Check_MK helpers were leaking memory. This can be configured +by changing the option "Check_MK check helpers" of the global setting "Logging of the core" +to e.g. Informational. + +In this mode the helper gathers information about some changed variables during runtime +and the memory usage. It also allows to debug different mechanics of the helpers. + +If you enabled this, each reload of the core (not restart) was triggering the memory +leak in the helpers. In extreme situations this could lead to duplication of the memory +usage on each reload.