| Summary: | digikam crashing while scanning >20000 pictures | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | andreas.tarp |
| Component: | Database-Scan | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | andreas.tarp |
| Priority: | NOR | ||
| Version: | 2.1.1 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 2.4.0 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
andreas.tarp
2011-10-28 16:34:38 UTC
Crash appear in Libpgf using OpenMP implementation for GCC. I have reproduced this crash some month ago, and it's due to OpenMP support in libpgf. I voluntary disabled OpenMP support with libpgf included in digiKam as 3rd party until this support become better. Q: How do you compile digiKam using OpenMP support especially with libpgf ? I want mean, how it's possible, because all releavant code is disabled ? Gilles Caulier Created attachment 64990 [details]
New crash information added by DrKonqi
digikam (2.1.1) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4
- What I was doing when the application crashed:
after first crash I restarted digikam and continued to scan the new pictures. After a while (new folders where shown in digikam one after another) digikam crashed again.
-- Backtrace (Reduced):
#14 0xb4c16e0b in qMalloc (size=112) at global/qmalloc.cpp:55
#15 0xb4c74514 in QVectorData::allocate (size=112, alignment=4) at tools/qvector.cpp:67
#16 0xb774e123 in malloc (aalloc=6, this=<optimized out>) at ../../include/QtCore/../../src/corelib/tools/qvector.h:393
#17 QVector<QSqlField>::realloc (this=0xc655258, asize=3, aalloc=6) at ../../include/QtCore/../../src/corelib/tools/qvector.h:466
#18 0xb774e39c in QVector<QSqlField>::append (this=0xc655258, t=...) at ../../include/QtCore/../../src/corelib/tools/qvector.h:549
Hi, I did not compile on my own. I am using digikam from kubuntu 11.10th repository. So maybe package maintainers are using old code? Cheers, Andreas Gilles Caulier <caulier.gilles@gmail.com> schrieb: >https://bugs.kde.org/show_bug.cgi?id=285194 > > > > > >--- Comment #1 from Gilles Caulier <caulier gilles gmail com> 2011-10-28 16:48:48 --- >Crash appear in Libpgf using OpenMP implementation for GCC. > >I have reproduced this crash some month ago, and it's due to OpenMP support in >libpgf. I voluntary disabled OpenMP support with libpgf included in digiKam as >3rd party until this support become better. > >Q: How do you compile digiKam using OpenMP support especially with libpgf ? I >want mean, how it's possible, because all releavant code is disabled ? > >Gilles Caulier > >-- >Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email >------- You are receiving this mail because: ------- >You reported the bug. digiKam 2.2.0 is out since few weeks. Crash still valid with this version ? Gilles Caulier Hi, digikam 2.2.0 is unfortunately not yet available in official kubuntu repositories. But I will try to set it up during next few days on a virtual machine to retest on 2.2.0 and tell you afterwards the result. Thanks already for this great application. Andreas Created attachment 65271 [details]
New crash information added by DrKonqi
digikam (2.2.0) on KDE Platform 4.7.2 (4.7.2) using Qt 4.7.4
- What I was doing when the application crashed:
Hi,
I was able to reproduce the crash also with digikam 2.2.0. I have installed 2.2.0 on a virtual machine and put around 14k pictures in the picture folder. First time scanning digikam did not crash, but after removing and storing the pictures a few more times in the picture folder resulted finally in digikam crashing again...
So, hope the new information are usefull and point into the same direction as on digikam 2.1.1.
BR, Andreas
-- Backtrace (Reduced):
#15 0x0047bbdd in Digikam::ImageInfoCache::dropInfo (this=0x9920818, infodata=0xa995c698) at /build/buildd/digikam-2.2.0/core/libs/database/imageinfocache.cpp:92
#16 0x004760e8 in Digikam::ImageInfo::~ImageInfo (this=0xaa4fecbc, __in_chrg=<optimized out>) at /build/buildd/digikam-2.2.0/core/libs/database/imageinfo.cpp:224
#17 0x004657d9 in Digikam::DatabaseThumbnailInfoProvider::thumbnailInfo (this=0x9922780, path=...) at /build/buildd/digikam-2.2.0/core/libs/database/databasethumbnailinfoprovider.cpp:45
#18 0x06e08b07 in Digikam::ThumbnailCreator::makeThumbnailInfo (this=0xa4de728, path=..., rect=...) at /build/buildd/digikam-2.2.0/core/libs/threadimageio/thumbnailcreator.cpp:345
#19 0x06e0c83c in Digikam::ThumbnailCreator::load (this=0xa4de728, path=..., rect=..., pregenerate=false) at /build/buildd/digikam-2.2.0/core/libs/threadimageio/thumbnailcreator.cpp:225
The last backtrace looks like a duplicate of 262077, fixed for digikam 2.3.0 Hi, seems like you are right. I upgraded my testmachine to 2.3.0 and was not able to reproduce the issue anymore. So sounds like my initial problem was solved already with 2.2.0, and the crash I experienced on 2.2.0 was solved in 2.3.0. So thanks a lot for the support and this great application, Andreas |