[Digikam-devel] Re: memory leak in trunk...

[Andi Clemens]

It should be mentioned that valgrind isn't always right, I had situations were 
it complained about not freed memory, although it definetly has been freed.
This happens especially when using threads.

Andi Clemens
-----------------
www.digikam.org

On Wednesday 01 December 2010 11:50:27 Gilles Caulier wrote:
> I agree with you.
> 
> What do you see in your computer with valgrind ? the same size ?
> 
> Gilles
> 
> 2010/12/1 Marcel Wiesweg <marcel.wiesweg at gmx.de>:
> >> ==14101== 1,390,426 (20 direct, 1,390,406 indirect) bytes in 1 blocks
> >> are definitely lost in loss record 6,807 of 6,808
> >> ==14101==    at 0x40244F0: operator new(unsigned int)
> >> (vg_replace_malloc.c:214) ==14101==    by 0x820FFB9:
> >> Digikam::DigikamImageDelegate::DigikamImageDelegate(Digikam::ImageCatego
> >> riz edView*) (digikamimagedelegate.cpp:62)
> > 
> > I dont understand that. "1 block" means that this is one single
> > allocation, doesnt it? The size of ImageCategoryDrawer, one d-pointer in
> > ImageCategoryDrawer, one d-pointer in KCategoryDrawer, should be
> > 2*sizeof(void*), 16 bytes, not 1.3MB!
> > And there is not more than one such object per digikam application, only
> > the main icon view uses it.
> > 
> > Marcel
> > _______________________________________________
> > Digikam-devel mailing list
> > Digikam-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/digikam-devel
> 
> _______________________________________________
> Digikam-devel mailing list
> Digikam-devel at kde.org
> https://mail.kde.org/mailman/listinfo/digikam-devel