Daemon: memory leak during call (TLS transport)
Issue generated from Tuleap's migration script. Originally submitted by: Guillaume Roguez (guillaume)
Memory leak seen using ASAN (address sanitizer) after a Ring call (memory leak displayed when application quit)
Direct leak of 1088 byte(s) in 1 object(s) allocated from: \#0 0x7ffff70f3ba9 in \_\_interceptor\_calloc (/lib64/libasan.so.2+0x98ba9) \#1 0x3c5043907e in gnutls\_priority\_init (/lib64/libgnutls.so.28+0x3c5043907e) \#2 0x6699bc in ring::SipTransportBroker::getTlsIceTransport(std::shared\_ptr<ring::IceTransport>, unsigned int, ring::tls::TlsParams const&) /home/yomgui/Projects/ring-daemon/src/sip/siptransport.cpp:454 \#3 0x4e6495 in ring::RingAccount::handleEvents() /home/yomgui/Projects/ring-daemon/src/ringdht/ringaccount.cpp:621 \#4 0x4e798b in ring::RingAccount::doRegister\_()::{lambda()\#3}::operator()() const (/home/yomgui/Projects/ring-daemon/bin/dring+0x4e798b) \#5 0x4f1c47 in \_M\_invoke /usr/include/c++/5.1.1/functional:1871 \#6 0x426cd3 in std::function<void ()>::operator()() const /usr/include/c++/5.1.1/functional:2271 \#7 0x5b71d3 in ring::Manager::pollEvents() /home/yomgui/Projects/ring-daemon/src/manager.cpp:1410 \#8 0x49b3a3 in DRing::pollEvents() /home/yomgui/Projects/ring-daemon/src/ring\_api.cpp:77 \#9 0x433180 in std::\_Function\_handler<void (), void (\*)()>::\_M\_invoke(std::\_Any\_data const&) (/home/yomgui/Projects/ring-daemon/bin/dring+0x433180) \#10 0x426cd3 in std::function<void ()>::operator()() const /usr/include/c++/5.1.1/functional:2271 \#11 0x4255f7 in EventCallback::call(DBus::DefaultTimeout&) const (/home/yomgui/Projects/ring-daemon/bin/dring+0x4255f7) \#12 0x3796a15142 in DBus::DefaultMainLoop::dispatch() (/lib64/libdbus-c++-1.so.0+0x3796a15142) \#13 0x3796a15dbb in DBus::BusDispatcher::enter() (/lib64/libdbus-c++-1.so.0+0x3796a15dbb) \#14 0x7fffffffdacf (<unknown module>) \#15 0x0 (<unknown module>)