[Digikam-devel] memory leak by Mr Valgrind

[Marcel Wiesweg]

> 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::ImageCategoriz
> edView*) (digikamimagedelegate.cpp:64)

Yes I know, this is an obvious leak, but:
Look at ImageDelegate::~ImageDelegate(). This destruction was crashing for a 
lot of people sometime last year. Crash was gone when we just leaked it. Not a 
satisfying solution, I have no idea why it crashed, it never did for me.