From: Marty K. <mrk...@co...> - 2011-04-13 10:48:58
|
Matej, I am starting to look at memory leaks in V3Channel. Could I get you to look. There are problems with just starting an IOC and stopping it without any activity. ==3595== LEAK SUMMARY: ==3595== definitely lost: 120 bytes in 5 blocks ==3595== indirectly lost: 0 bytes in 0 blocks ==3595== possibly lost: 3,791 bytes in 62 blocks ==3595== still reachable: 600,859 bytes in 11,127 blocks ==3595== suppressed: 0 bytes in 0 blocks The first few reports are: Thread 1: ==3595== 14 bytes in 1 blocks are possibly lost in loss record 245 of 787 ==3595== at 0x4006241: operator new(unsigned int) (vg_replace_malloc.c:255) ==3595== by 0x56BAD05: std::string::_Rep::_S_create(unsigned int, unsigned int, std::allocator<char> const&) (in /usr/lib/libstdc++.so.6.0.14) ==3595== by 0x4105509: epics::pvAccess::SystemConfigurationImpl::getPropertyAsBoolean(std::string, bool) (basic_string.tcc:138) ==3595== by 0x411CAEC: epics::pvAccess::ServerContextImpl::loadConfiguration() (serverContext.cpp:86) ==3595== by 0x411D801: epics::pvAccess::ServerContextImpl::ServerContextImpl() (serverContext.cpp:43) ==3595== by 0x403CDA3: MyRun::MyRun() (startPVAccessServer.cpp:47) ==3595== by 0x403CE9D: startPVAccessServerCallFunc(iocshArgBuf const*) (startPVAccessServer.cpp:83) ==3595== by 0x42A76E8: iocshBody (iocsh.cpp:743) ==3595== by 0x804A90C: main (exampleMain.cpp:17) I ran valgrind via the statement: valgrind --log-file=temp --leak-check=full ../../bin/linux-x86/example st.cmd Then just immediately exit. Marty |