[digikam] [Bug 335937] New: Crash on startup. ConnectionTest still in use. terminate called after throwing an instance of 'St9bad_alloc'

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 335937] New: Crash on startup. ConnectionTest still in use. terminate called after throwing an instance of 'St9bad_alloc'

Gerrit Holl-2
https://bugs.kde.org/show_bug.cgi?id=335937

            Bug ID: 335937
           Summary: Crash on startup.  ConnectionTest still in use.
                    terminate called after throwing an instance of
                    'St9bad_alloc'
    Classification: Unclassified
           Product: digikam
           Version: 3.4.0
          Platform: Ubuntu Packages
               URL:
                OS: Linux
            Status: UNCONFIRMED
          Severity: grave
          Priority: NOR
         Component: general
          Assignee: [hidden email]
          Reporter: [hidden email]

When I start digikam, I briefly get the splash screen, until "Initializing main
view".  Then it crashes.  The output is as follows:

$ digikam --version
Qt: 4.8.4
KDE Development Platform: 4.11.5
digiKam: 3.4.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.
"/org/freedesktop/UDisks2/drives/WDC_WD2500BEVT_08A23T1_WD_WX51A8054109" :
property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/WDC_WD2500BEVT_08A23T1_WD_WX51A8054109" :
property "Device" does not exist
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 after throwing an instance of 'St9bad_alloc'
  what():  std::bad_alloc
terminate called recursively
terminate called recursively
terminate called recursively

I tried to reboot, I tried to clear the configuration files and/or the
database, but nothing changed the situation.  The output varies a little bit
from time to time, such as the number of times "QThread::start: Thread creation
error: Resource temporarily unavailable" is printed.  Sometimes it also shows
"Unable to start Dr. Konqi".

Reproducible: Always

Steps to Reproduce:
1. Start digikam
2. Crash
3.
Actual Results:  
It crashes with signal 255.

Expected Results:  
Start digikam.

$ uname -a
Linux naimakka 3.11.0-22-generic #38-Ubuntu SMP Thu May 15 20:47:00 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux

$ dpkg -s digikam
Package: digikam
Status: install ok installed
Priority: optional
Section: graphics
Installed-Size: 15832
Maintainer: Kubuntu Developers <[hidden email]>
Architecture: amd64
Version: 4:3.4.0-1ubuntu3
Depends: kde-runtime, libc6 (>= 2.14), libgcc1 (>= 1:4.1.1), libgphoto2-6 (>=
2.4.10.1), libgphoto2-port10 (>= 2.5.2), libjasper1, libjpeg8 (>= 8c),
libkdcraw22 (>= 4:4.9.90), libkdecore5 (>= 4:4.10), libkdeui5 (>= 4:4.10),
libkexiv2-11 (>= 4:4.10.80), libkface2 (>= 1.0~digikam3.4.0), libkfile4 (>=
4:4.10), libkgeomap1 (>= 1.0~digikam3.4.0), libkhtml5 (>= 4:4.10), libkio5 (>=
4:4.10), libkipi11 (>= 4:4.9.80), libknotifyconfig4 (>= 4:4.10), libkparts4 (>=
4:4.10), liblcms2-2 (>= 2.2+git20110628), liblensfun0, liblqr-1-0 (>= 0.4.0),
libopencv-core2.4, libpgf6 (>= 6.12.24+ds1), libphonon4 (>= 4:4.2.0),
libpng12-0 (>= 1.2.13-4), libqt4-dbus (>= 4:4.5.3), libqt4-qt3support (>=
4:4.5.3), libqt4-sql (>= 4:4.5.3), libqt4-xml (>= 4:4.5.3), libqtcore4 (>=
4:4.8.0), libqtgui4 (>= 4:4.8.0), libsolid4 (>= 4:4.10), libsqlite0 (>=
2.8.17), libstdc++6 (>= 4.6), libthreadweaver4 (>= 4:4.10), libtiff5 (>>
4.0.0-1~), libx11-6, phonon, perl, libqt4-sql-sqlite, digikam-data (=
4:3.4.0-1ubuntu3)
Recommends: www-browser, kipi-plugins, ffmpegthumbs | mplayerthumbs
Suggests: digikam-doc, systemsettings
Conffiles:
 /etc/apparmor.d/usr.sbin.mysqld-digikam 65a44f572e6918c9db470242fd69397f

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 335937] Crash on startup. ConnectionTest still in use. terminate called after throwing an instance of 'St9bad_alloc'

Gerrit Holl-2
https://bugs.kde.org/show_bug.cgi?id=335937

--- Comment #1 from Gerrit Holl <[hidden email]> ---
I upgraded to 3.5.0.  The crash persists and is reproducable, but the error
messages are not always the same:

$ 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
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
Unable to start Dr. Konqi
Not forwarding the crash to Apport.
$ 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.
terminate called recursively
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
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
Unable to start Dr. Konqi
terminate called after throwing an instance of 'St9bad_alloc'
terminate called recursively
terminate called recursively
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
digikam: Fatal IO error 9 (Bad file descriptor) on X server :0.0.
  what():  std::bad_alloc
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
terminate called recursively
Not forwarding the crash to Apport.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 335937] Crash on startup. ConnectionTest still in use. terminate called after throwing an instance of 'St9bad_alloc'

Gerrit Holl-2
In reply to this post by Gerrit Holl-2
https://bugs.kde.org/show_bug.cgi?id=335937

--- Comment #2 from Gerrit Holl <[hidden email]> ---
Created attachment 87066
  --> https://bugs.kde.org/attachment.cgi?id=87066&action=edit
output of 'strace -o -ff' in a tar.gz (22 strace files)

output of 'strace -o -ff digikam' in a tar.gz (22 strace files).

This is a fully clean install (removed apps/digikam and config/digikamrc, as
well as thumbs.db and digikam4.db).

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 335937] Crash on startup. ConnectionTest still in use. terminate called after throwing an instance of 'St9bad_alloc'

Gerrit Holl-2
In reply to this post by Gerrit Holl-2
https://bugs.kde.org/show_bug.cgi?id=335937

Gerrit Holl <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|3.4.0                       |3.5.0

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 335937] Crash on startup. ConnectionTest still in use. terminate called after throwing an instance of 'St9bad_alloc'

Gilles Caulier-4
In reply to this post by Gerrit Holl-2
https://bugs.kde.org/show_bug.cgi?id=335937

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[hidden email]
         Resolution|---                         |BACKTRACE

--- Comment #3 from Gilles Caulier <[hidden email]> ---
Strace is not informative about the problem. Please run digiKam in GDB as
explained here and give us a suitable backtrace to hack...

http://www.digikam.org/contrib

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 335937] Crash on startup. ConnectionTest still in use. terminate called after throwing an instance of 'St9bad_alloc'

Gerrit Holl-2
In reply to this post by Gerrit Holl-2
https://bugs.kde.org/show_bug.cgi?id=335937

Gerrit Holl <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|BACKTRACE                   |---

--- Comment #4 from Gerrit Holl <[hidden email]> ---
Oops, I didn't notice the gdb comment until now.  However, I have discovered a
very valuable piece of additional information.

The crash happens if I set a too low ulimit.

With ulimit -v 1500000, it crashes.
With ulimit -v 4000000, it does not crash.

Please let me know if you are able to reproduce the bug with this information.

Will I need to compile digikam from source for gdb to provide useful
information?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 335937] Crash on start-up due to user resource limitations set in PAM configuration

Gilles Caulier-4
In reply to this post by Gerrit Holl-2
https://bugs.kde.org/show_bug.cgi?id=335937

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Crash on startup.           |Crash on start-up due to
                   |ConnectionTest still in     |user resource limitations
                   |use.  terminate called      |set in PAM configuration
                   |after throwing an instance  |
                   |of 'St9bad_alloc'           |

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 335937] Crash on start-up due to user resource limitations set in PAM configuration

Gilles Caulier-4
In reply to this post by Gerrit Holl-2
https://bugs.kde.org/show_bug.cgi?id=335937

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |
         Resolution|---                         |BACKTRACE
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #5 from Gilles Caulier <[hidden email]> ---
Didi you try to get a suitable backtrace with GDB, installing digiKam debug
package ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 335937] Crash on start-up due to user resource limitations set in PAM configuration

Gilles Caulier-4
In reply to this post by Gerrit Holl-2
https://bugs.kde.org/show_bug.cgi?id=335937

--- Comment #6 from Gilles Caulier <[hidden email]> ---
New digiKam 4.11.0 is available with official PKG installer for OSX.

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 335937] Crash on start-up due to user resource limitations set in PAM configuration

Gilles Caulier-4
In reply to this post by Gerrit Holl-2
https://bugs.kde.org/show_bug.cgi?id=335937

--- Comment #7 from Gilles Caulier <[hidden email]> ---
digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 335937] Crash on start-up due to user resource limitations set in PAM configuration

Gerrit Holl-2
In reply to this post by Gerrit Holl-2
https://bugs.kde.org/show_bug.cgi?id=335937

--- Comment #8 from Gerrit Holl <[hidden email]> ---
On 20 August 2015 at 07:50, Gilles Caulier <[hidden email]> wrote:
> https://bugs.kde.org/show_bug.cgi?id=335937
>
> --- Comment #7 from Gilles Caulier <[hidden email]> ---
> digiKam 4.12.0 is out :
>
> https://www.digikam.org/node/741
>
> We need a fresh feedback using this release please...

Ok, I will have a look later.

Gerrit.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

[digikam] [Bug 335937] Crash on start-up due to user resource limitations set in PAM configuration

bugzilla_noreply
In reply to this post by Gerrit Holl-2
https://bugs.kde.org/show_bug.cgi?id=335937

[hidden email] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|general                     |Database-Scan
   Version Fixed In|                            |5.1.0
         Resolution|BACKTRACE                   |FIXED

--- Comment #9 from [hidden email] ---
This problem is not reproducible with last 5.0.0.
I close this file now. Don't hesitate to re-open it if necessary.
Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel