[Digikam-devel] memory leak by Mr Valgrind

Gilles Caulier caulier.gilles at gmail.com
Tue Mar 13 22:29:32 GMT 2012


Marcel,

Another one in Collection Manager :

==7873== 112 bytes in 2 blocks are possibly lost in loss record 8,145 of 10,147
==7873==    at 0x4C251D7: operator new(unsigned long) (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==7873==    by 0x8260539:
Digikam::CollectionManager::updateLocations()
(collectionmanager.cpp:1559)
==7873==    by 0x825C73C: Digikam::CollectionManager::refresh()
(collectionmanager.cpp:763)
==7873==    by 0x8266F95:
Digikam::DatabaseAccess::checkReadyForUse(Digikam::InitializationObserver*)
(databaseaccess.cpp:314)
==7873==    by 0x5EDE44: Digikam::ScanController::run() (scancontroller.cpp:656)
==7873==    by 0xC6DA1E4: ??? (in /usr/lib64/libQtCore.so.4.7.4)
==7873==    by 0xCB00D24: start_thread (in /lib64/libpthread-2.12.1.so)
==7873==    by 0xDAF423C: clone (in /lib64/libc-2.12.1.so)

Gilles Caulier



More information about the Digikam-devel mailing list