Memory leak in Qt signal and slots

Question

Hello, I am running valgrind on my Qt code,and even on successful exit of the application, get the following report from valgrind

8,832 bytes in 92 blocks are still reachable in loss record 12 of 12

at 0x4025390: operator new(unsigned int) (vg_replace_malloc.c:214)
==3339== by 0x4B75F05: QMutex::QMutex(QMutex::RecursionMode) (qmutex.cpp:123) ==3339== by 0x4B77602: QMutexPool::get(void const*) (qmutexpool.cpp:137)
==3339== by 0x4CA0EC2: signalSlotLock(QObject const*) (qobject.cpp:112)
==3339== by 0x4CA3939: QMetaObjectPrivate::connect(QObject const*, int, QObject const*, int, int, int*) (qobject.cpp:2900)
==3339== by 0x4CA5C00: QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) (qobject.cpp:2599)

I disconnect all signal connections and also delete the objects. The above mentioned leak increases if i increase the amount of signal and slot connections?

Can anybody help with this?

Answer 1

Memory that is "still reachable" isn't actually leaked memory. How many errors are listed in your "ERROR SUMMARY"?

Also, see http://stackoverflow.com/questions/1593717/is-anyone-using-valgrind-and-qt.