Crash on startup. ConnectionTest still in use. terminate called after throwing an instance of 'St9bad_alloc'

[Gerrit Holl-2]

Hi,

I am unable to start digikam 3.5.0 due to a crash on startup.  I get
the splash screen until "Initializing main view", then it crashes.
The output is shown below.  The problem persists after I completely
remove digikam, remove ~/.kde/share/config/digikamrc,
.kde/share/apps/digikam, my thumbnails database, and my digikam4.db,
reboot, and install digikam again.  I am running xubuntu saucy (XFCE).

The output is not completely identical every time, but the output
shown below is typical.  I have also uploaded an archive with the
output of "strace -o -ff digikam" to
https://bugs.kde.org/attachment.cgi?id=87066

I have found some pointers on the web of people with similar problems,
but for them upgrading and removing/reinstalling the configuration
files solved the problem.  It doesn't for me.  I'm surprised that I
don't find other references; I suppose it must be due to some
combination of libraries that I have.  How would I proceed to
troubleshoot this issue?

$ digikam --version
Qt: 4.8.4
KDE Development Platform: 4.13.0
digiKam: 3.5.0
$ digikam
Object::connect: No such signal
org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal
org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is
still in use, all queries will cease to work.
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
QThread::start: Thread creation error: Resource temporarily unavailable
terminate called recursively
KCrash: Application 'digikam' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
Error: Could not determine display.
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly
terminate called recursively
terminate called recursively
terminate called recursively
Not forwarding the crash to Apport.

regards,
Gerrit.

--
Exploring space at http://gerrit-explores.blogspot.com/
Personal homepage at http://www.topjaklont.org/
Asperger Syndroom: http://www.topjaklont.org/nl/asperger.html
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[carl33914]

Probably not much help, but info anyway.
I run digikam on openSUSE 13.1/KDE

Here is what I get:

digikam --version
Qt: 4.8.5
KDE Development Platform: 4.13.1
digiKam: 4.0.0

On the oS forums, a typical configuration debug strategy is to create a
new user account and try from that "clean" setup environment.

Good luck in your hunt
On 06/08/2014 12:19 AM, Gerrit Holl wrote:

> Hi,
>
> I am unable to start digikam 3.5.0 due to a crash on startup.  I get
> the splash screen until "Initializing main view", then it crashes.
> The output is shown below.  The problem persists after I completely
> remove digikam, remove ~/.kde/share/config/digikamrc,
> .kde/share/apps/digikam, my thumbnails database, and my digikam4.db,
> reboot, and install digikam again.  I am running xubuntu saucy (XFCE).
>
> The output is not completely identical every time, but the output
> shown below is typical.  I have also uploaded an archive with the
> output of "strace -o -ff digikam" to
> https://bugs.kde.org/attachment.cgi?id=87066
>
> I have found some pointers on the web of people with similar problems,
> but for them upgrading and removing/reinstalling the configuration
> files solved the problem.  It doesn't for me.  I'm surprised that I
> don't find other references; I suppose it must be due to some
> combination of libraries that I have.  How would I proceed to
> troubleshoot this issue?
>
> $ digikam --version
> Qt: 4.8.4
> KDE Development Platform: 4.13.0
> digiKam: 3.5.0
> $ digikam
> Object::connect: No such signal
> org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
> Object::connect: No such signal
> org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
> QSqlDatabasePrivate::removeDatabase: connection 'ConnectionTest' is
> still in use, all queries will cease to work.
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> QThread::start: Thread creation error: Resource temporarily unavailable
> terminate called recursively
> KCrash: Application 'digikam' crashing...
> KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
> Error: Could not determine display.
> KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi directly
> terminate called recursively
> terminate called recursively
> terminate called recursively
> Not forwarding the crash to Apport.
>
> regards,
> Gerrit.
>

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gerrit Holl-2]

Hello all,

I found the offending piece of configuration.

The aforementioned crash happens whet digikam runs out of memory.

If I set 'ulimit -v 1500000', it crashes.

If I set 'ulimit -v 4000000', it runs succesfully.

I will add this information to the bug report.  At the very least,
digikam could fail more graciously if it can't get the memory it needs
(note that it is NOT using 1500000 memory!).

regards,
Gerrit Holl.
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users