[Digikam-devel] Re: KCategoryDrawer and memory leak...

[Marcel Wiesweg]

> ==16673== 3,152 (12 direct, 3,140 indirect) bytes in 1 blocks are
> definitely lost in loss record 6,503 of 6,663
> ==16673==    at 0x40244F0: operator new(unsigned int)
> (vg_replace_malloc.c:214) ==16673==    by 0x82B6F71:
> Digikam::DigikamImageDelegate::DigikamImageDelegate(Digikam::ImageCategoriz
> edView*) (digikamimagedelegate.cpp:63)

See destructor ~ImageDelegate.
It's a leak, but the deletion crashes (230515) for a lot of people, never for 
me, and I dont know why.

KCategoryDrawer (V1) works just fine for us, if just for the compiler 
warnings, we can use V2 or V3 or whatever.

Marcel