> Must be the recent DNS changes. From a quick look I don't see where
> it's leaking but my local perftools unfortunately doesn't report it.
> 
> Can we get the output of that pprof command?

That particular one is gone now, but here's another:

(pprof) top
Total: 4 objects
       2  50.0%  50.0%        4 100.0% DNS_Mgr::AddResult 
/home/jsiwek/bro/src/DNS_Mgr.cc:708
       2  50.0% 100.0%        2  50.0% copy_string 
/home/jsiwek/bro/src/util.cc:154
       0   0.0% 100.0%        2  50.0% DNS_Mapping::DNS_Mapping 
/home/jsiwek/bro/src/DNS_Mgr.cc:174
       0   0.0% 100.0%        4 100.0% DNS_Mgr::DoProcess 
/home/jsiwek/bro/src/DNS_Mgr.cc:1319
       0   0.0% 100.0%        4 100.0% DNS_Mgr::Process 
/home/jsiwek/bro/src/DNS_Mgr.cc:1269
       0   0.0% 100.0%        4 100.0% __libc_start_main ??:0
       0   0.0% 100.0%        4 100.0% main /home/jsiwek/bro/src/main.cc:1073
       0   0.0% 100.0%        4 100.0% net_run /home/jsiwek/bro/src/Net.cc:446

It's reproducible for me if need to interactively run it yourself, ssh in to 
brotestbed and you can compile your own version to test with.

    Jon 

> 
> Robin
> 
> ----- Forwarded message from [email protected] -----
> 
> Date: Mon, 5 Nov 2012 20:14:32 -0600 (CST)
> From: [email protected]
> To: [email protected]
> Subject: [Bro-Commits-Internal] UnitTests - Build # 454 - Still Failing!
> Message-ID: 
> <1781954848.7.1352168072776.javamail.jenk...@brotestbed.ncsa.illinois.edu>
> Reply-To: [email protected]
> 
> [...]
> 
> core.leaks.dns ... failed
>  % 'HEAP_CHECK_DUMP_DIRECTORY=. HEAPCHECK=local bro -m -r 
> $TRACES/wikipedia.trace 
> /home/jenkins/workspace/UnitTests/bro/testing/btest/.tmp/core.leaks.dns/dns.bro'
>  failed unexpectedly (exit code -6)
>  % cat .stderr
>  WARNING: Perftools heap leak checker is active -- Performance may suffer
>  Leak check net_run detected leaks of 233 bytes in 4 objects
>  The 2 largest leaks:
>  Leak of 208 bytes in 2 objects allocated from:
>  @ 6ae0b9
>  @ 6b0f76
>  @ 6b0ba3
>  @ 77770f
>  @ 6675c0
>  @ 39d8e1ecdd
>  Leak of 25 bytes in 2 objects allocated from:
>  @ 669df9
>  @ 6ab75b
>  @ 6ae0d1
>  @ 6b0f76
>  @ 6b0ba3
>  @ 77770f
>  @ 6675c0
>  @ 39d8e1ecdd
> 
> 
>  If the preceding stack traces are not enough to find the leaks, try running 
> THIS shell command:
> 
>  pprof bro "./bro.31993.net_run-end.heap" --inuse_objects --lines --heapcheck 
>  --edgefraction=1e-10 --nodefraction=1e-10 --gv
> 
>  If you are still puzzled about why the leaks are there, try rerunning this 
> program with HEAP_CHECK_TEST_POINTER_ALIGNMENT=1 and/or with 
> HEAP_CHECK_MAX_POINTER_OFFSET=-1
>  If the leak report occurs in a small fraction of runs, try running with 
> TCMALLOC_MAX_FREE_QUEUE_SIZE of few hundred MB or with 
> TCMALLOC_RECLAIM_MEMORY=false, it might help find leaks more repeatably
>  Memory leaks - aborting.
> 
> core.leaks.remote ... ok
> core.leaks.ayiya ... ok
> 1 of 13 tests failed
> Build step 'Execute shell' marked build as failure
> Recording test results
> Email was triggered for: Failure
> Sending email for trigger: Failure
> 
> _______________________________________________
> bro-commits-internal mailing list
> [email protected]
> http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-commits-internal
> 
> 
> ----- End forwarded message -----
> 
> 
> -- 
> Robin Sommer * Phone +1 (510) 722-6541 * [email protected]
> ICSI/LBNL    * Fax   +1 (510) 666-2956 *   www.icir.org
> _______________________________________________
> bro-dev mailing list
> [email protected]
> http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
> 


_______________________________________________
bro-dev mailing list
[email protected]
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev

Reply via email to