BRO valgrind test

I'm wonderingif anyone can help me with this.
I ran valgrind against an instance of BRO. I found memory leaks (refering to operator new())
in the valgrind logs.
Am i missing something or does the memory pool gets refreshed (over time) depending on traffic presence or absence.

thanks
- Vish

Vishwanathan Krishnamurthy wrote:

I'm wonderingif anyone can help me with this.
I ran valgrind against an instance of BRO. I found memory leaks (refering to operator new())
in the valgrind logs.
Am i missing something or does the memory pool gets refreshed (over time) depending on traffic presence or absence.

thanks
- Vish

_______________________________________________
Bro mailing list
bro@bro-ids.org
http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/bro

The interface between the event engine and the policy side of bro can
cause issues for valgrind (and many other memory testing programs).
There has been considerable effort to reduce issues with memory leaks
for some time now, and as far as I know there are no major issues.

If there are specific examples, feel free to forward them to the list as
we are always looking for improvements.

thanks!

scott

Valgrind usually reports a couple of leaks in the script parser.
These are rather minor though as their total volume is small and
they only occur once during initialization.

However, if you see any leak reported during Bro's main processing
then that's a significant bug; every leak in the main loop may drive
Bro to memory exhaustion eventually. In this case, could you please
mail us the valgrind logs?

Thanks,

Robin