Ivan,
2006/8/31, Ivan Verbeeck <user-5c6357abd073@xymon.invalid>:
Etienne,
I'll fix it that way.
Thanx for your time!
Good news, finally, I found the bug... There were a bad initialization
in the msgs agent in the function which build the description field.
So, there were always 32 bytes which were going into the sky for each
matched event :-)
I build a new version of msgs which fix the problem.
You may download the new version of the msgs agent from :
http://bbwin.sourceforge.net/download/msgs.zip
To install it :
- stop bbwin service
- unzip the msgs.zip file and overwrite the old msgs.dll
- start bbwin service
Then the memory should be ok.
Anyway, the fix will be included into BBWin 0.9.
So, you won't have to schedule an automatic restart of the BBWin which
was for me very offensive :-)
Thank you very much for your report,
I also have to thank the company codework for their great profiler and
memory leak software called GlowCode.
Best regards,
--
Etienne GRIGNON