We are using POCO Version 1.4.5. And we suspect we are getting some memory leaks from this version of POCO. Below is the stack trace we got when we checked for leaks in our code with Valgrind memory check tool.
==16045== 304 bytes in 1 blocks are possibly lost in loss record 12 of 13
==16045== at 0x4C25EFE: calloc (vg_replace_malloc.c:566)
==16045== by 0x401110E: _dl_allocate_tls (in /lib64/ld-2.11.1.so)
==16045== by 0x6768C62: pthread_create@@GLIBC_2.2.5 (in /lib64/libpthread-2.11.1.so)
==16045== by 0x4F1CFF2: Poco::ThreadImpl::startImpl(Poco::Runnable&) (in /usr/lib64/libPocoFoundation.so.9)
Above is the top part stack trace we obtained through valgrind memory check tool.
A call to this function " Poco::ThreadImpl::startImpl(Poco::Runnable&)" is made when a thread is started by an agent in our code. This thread is used for listening Break Requests from various processes. For eg : (CNTRL<c>) is one such break request.
The class (in our code) which implements handling of these break requests, inherits from the POCO class --> "Poco::Runnable"
The Valgrind memory check tool reports memory leaks from this point.
Can you please provide support on this issue, as we have faced this kind of memory leak at many places in our code.