[digikam] [Bug 381877] Digikam start allocating all memory when scans a new collection.
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Sat Jul 15 11:11:47 BST 2017
https://bugs.kde.org/show_bug.cgi?id=381877
--- Comment #30 from caulier.gilles at gmail.com ---
2,874,814 bytes in 59 blocks are still reachable in loss record 42,450 of
42,454
==14781== by 0xE57BA04: cmsOpenIOhandlerFromMem (in
/usr/lib/liblcms2.so.2.0.8)
==14781== by 0xE57D2C4: cmsOpenProfileFromMemTHR (in
/usr/lib/liblcms2.so.2.0.8)
==14781== by 0x5D19CA8: Digikam::IccProfile::open() (in
/usr/lib/libdigikamcore.so.5.6.0)
==14781== by 0x5D24328: Digikam::IccSettings::Private::scanDirectory(QString
const&, QStringList const&, QList<Digikam::IccProfile>*) (in
/usr/lib/libdigikamcore.so.5.6.0)
==14781==
==14781== 2,876,289 bytes in 59 blocks are still reachable in loss record
42,451 of 42,454
==14781== by 0x87AF923: QArrayData::allocate(unsigned long, unsigned long,
unsigned long, QFlags<QArrayData::AllocationOption>) (in
/usr/lib/libQt5Core.so.5.9.1)
==14781== by 0x87B23C3: QByteArray::resize(int) (in
/usr/lib/libQt5Core.so.5.9.1)
==14781== by 0x88B410D: QIODevice::readAll() (in
/usr/lib/libQt5Core.so.5.9.1)
==14781== by 0x5D1970F: Digikam::IccProfile::data() (in
/usr/lib/libdigikamcore.so.5.6.0)
==14781== by 0x5D19BAF: Digikam::IccProfile::open() (in
/usr/lib/libdigikamcore.so.5.6.0)
This happen when digiKAm scan ICC color profiles from your system. Typically,
you have the color management turned on.
Turn off CM and try again. Perhaps you have corrupted ICC color profile on your
system.
Gilles Caulier
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Digikam-devel
mailing list