[Digikam-devel] [Bug 180224] New: memory leakage in image editor?

Olleg Samoylov olleg_s at mail.ru
Sat Jan 10 09:37:37 GMT 2009


http://bugs.kde.org/show_bug.cgi?id=180224

           Summary: memory leakage in image editor?
           Product: digikam
           Version: unspecified
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel at kde.org
        ReportedBy: olleg_s at mail.ru


Version:           0.9.5-beta2 (using KDE 3.5.10)
Compiler:          gcc 4.3.2 amd64
OS:                Linux
Installed from:    Ubuntu Packages

digikam crashes when I sequencely edit several (~10) huge images (16 bit
tiffs). Console output:

QFile::open: No file name specified
lcms: Error #12288; Read from memory error. Got 0 bytes, block should be of 128
bytes
lcms: Error #12288; Corrupted memory profile
QComboBox::setCurrentItem: (unnamed) Index 3 out of range
JPEG image preview size: (770 x 1024) pixels - 75105 bytes
Exif orientation tag set to: 1
Cannot save metadata using Exiv2  (Error #31: Writing to %2 images is not
supported)
Exif Orientation: 1
QFile::open: No file name specified
lcms: Error #12288; Read from memory error. Got 0 bytes, block should be of 128
bytes
lcms: Error #12288; Corrupted memory profile
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted (core dumped)

Also I have huge enough core.bz2=846M, not sure how to send it.


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Digikam-devel mailing list