Commit f552d18e authored by Dominik Charousset's avatar Dominik Charousset

Remove logging from broker destructor

When building CAF with logging enabled, some brokers can be destroyed after the
logging singleton has been destroyed, resulting in the (lazy) construction of
another logger which then causes a memory leak.
parent e8ddcf31
......@@ -98,7 +98,7 @@ void abstract_broker::cleanup(uint32_t reason) {
}
abstract_broker::~abstract_broker() {
CAF_LOG_TRACE("");
// nop
}
void abstract_broker::configure_read(connection_handle hdl,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment