https://bugs.kde.org/show_bug.cgi?id=323888

Ritesh Raj Sarraf <kde-bugs@researchut.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kde-bugs@researchut.com

--- Comment #56 from Ritesh Raj Sarraf <kde-bugs@researchut.com> ---
(In reply to comment #41)
> The huge memory leak is already fixed. I miss libPGF memory
> corruption/leakto be fixed. I waiting libpgf feedback for that. 
> 
> Note: libpgf problems already exist in previous versions...
> 
> Gilles Caulier

@Gilles, I don't think the problem lies with libPGF.

First based on the advise, I recompiled libPGF as was recommended. That did not
help.

Then, I recompiled Digikam (4.0 Beta 4) with internal libPGF support. It still
loses memory at the same insane rate.


digiKam version 4.0.0-beta4
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibEigen: 3.2.1
LibExiv2: 0.23
LibJPEG: 80
LibJasper: 1.900.1
LibKDE: 4.12.4
LibKExiv2: 2.3.1
LibKGeoMap: 2.0.0
LibKdcraw: 2.3.1
LibLCMS: 2060
LibLensFun: 0.2.8-0
LibPGF: 6.13.45 - internal library
LibPNG: 1.2.50
LibQt: 4.8.6
LibRaw: 0.15.3
LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler Copyright
(c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.16.5 (stable version)
Parallelized PGF codec: No
Parallelized demosaicing: No
RawSpeed codec support: No
Database backend: QSQLITE
Kipi-Plugins: 4.0.0-beta4
LibGphoto2: 2.5.4
LibKface: 3.0.0
LibKipi: 2.1.0
LibOpenCV: 2.4.8

-- 
You are receiving this mail because:
You are watching all bug changes.