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

[Gilles Caulier]

In all case, KDE API said that KCategoryDrawer V1 is obsolete and unmaintained.

At least V2 need to be used instead, or better V3.

I propose to patch code to use V1 for old KDE < 4.4, V2 for KDE 4.4.x,
V3 for KDE > 4.5

What do you think about ?

Gilles Caulier

2010/11/6 Gilles Caulier <caulier.gilles at gmail.com>:
> Ok, i remember
>
> which KDE4 version you use ?
>
> Gilles Caulier
>
> 2010/11/3 Marcel Wiesweg <marcel.wiesweg at gmx.de>:
>>
>>> ==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
>> _______________________________________________
>> Digikam-devel mailing list
>> Digikam-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/digikam-devel
>>
>