# Threaded logging about to be merged

**URL:** https://community.zeek.org/t/threaded-logging-about-to-be-merged/2278
**Category:** Development
**Tags:** development
**Created:** [April 4, 2012, 7:59pm UTC](https://community.zeek.org/t/threaded-logging-about-to-be-merged/2278 "2012-04-04T19:59:44Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![robin](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/robin/32/599_2.png) [@robin](https://community.zeek.org/u/robin)
#### Post date: [April 4, 2012, 7:59pm UTC](https://community.zeek.org/t/threaded-logging-about-to-be-merged/2278/1 "2012-04-04T19:59:44Z")

</div>

A heads-up: It looks good on my cluster, so I'll be merging the  
threaded logging into master soon now. It took a while to find the  
real problem but on the upside, I'm now pretty sure that there aren't  
furhter leaks. 🙂

Also, the code now automatically links to tcmalloc when it finds it.  
At least on FreeBSD that not only helps with memory usage but also  
significantly reduces CPU (and that even if no threads are used at  
all).

Robin

---

<div class="post-metadata">

### Author: ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)
#### Post date: [May 6, 2022, 3:40pm UTC](https://community.zeek.org/t/threaded-logging-about-to-be-merged/2278/2 "2022-05-06T15:40:17Z")

</div>


