[Digikam-devel] memory leak by Mr Valgrind

[Gilles Caulier]

Marcel, i found this new allocation from image delegate class not
cleaned in destructor :

==14218== 496 (48 direct, 448 indirect) bytes in 1 blocks are
definitely lost in loss record 9,323 of 10,393
==14218==    at 0x4C251D7: operator new(unsigned long) (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==14218==    by 0x62230A:
Digikam::DigikamImageDelegatePrivate::init(Digikam::DigikamImageDelegate*,
Digikam::ImageCategorizedView*) (digikamimagedelegate.cpp:52)
==14218==    by 0x62240E:
Digikam::DigikamImageDelegate::DigikamImageDelegate(Digikam::ImageCategorizedView*)
(digikamimagedelegate.cpp:64)
==14218==    by 0x61D0DC:
Digikam::DigikamImageView::DigikamImageView(QWidget*)
(digikamimageview.cpp:98)
==14218==    by 0x6772EA: Digikam::StackedView::StackedView(QWidget*)
(stackedview.cpp:101)
==14218==    by 0x67A6B3: Digikam::DigikamView::DigikamView(QWidget*,
Digikam::DigikamModelCollection*) (digikamview.cpp:203)
==14218==    by 0x59145D: Digikam::DigikamApp::setupView() (digikamapp.cpp:517)
==14218==    by 0x58FF9C: Digikam::DigikamApp::DigikamApp() (digikamapp.cpp:257)
==14218==    by 0x6CB5D2: main (main.cpp:188)

Gillles