qiv crashed with SIGABRT in gdk_event_dispatch()

[Edward Donovan]

Came back to the computer and found qiv had crashed while I was away. No bright ideas about what triggered it. But I can note that I had run it recursively to scan a pretty big directory tree, about sixty thousand files, mostly images. It behaved fine when I was interacting with it. And multiple qiv processes were running, FWIW.

Thanks.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: qiv 2.2.4-1
ProcVersionSignature: Ubuntu 3.7.0-6.14-generic 3.7.0
Uname: Linux 3.7.0-6-generic x86_64
ApportVersion: 2.7-0ubuntu1
Architecture: amd64
Date: Thu Dec 13 02:52:05 2012
ExecutablePath: /usr/bin/qiv
MarkForUpload: True
ProcCmdline: qiv -fmru .
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=<set>
Signal: 6
SourcePackage: qiv
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
Title: qiv crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to raring on 2012-06-14 (182 days ago)
UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 gdk_event_dispatch (source=source@entry=0x126ffa0, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/gtk+2.0-2.24.13/gdk/x11/gdkevents-x11.c:2403
 g_main_dispatch (context=0x1270090) at /build/buildd/glib2.0-2.34.3/./glib/gmain.c:2715
 g_main_context_dispatch (context=context@entry=0x1270090) at /build/buildd/glib2.0-2.34.3/./glib/gmain.c:3219

[Sasa Paporovic (melchiaros)]

Reported upstream with mail to the developer of qiv:

<email address hidden>

[Sasa Paporovic (melchiaros)]

@ Edward

One of the qiv developers has answered to the e-mail notification.

Could you please answer his furhter question directly per mail.

I want to get out as a communication bridge(not really needed one).

He wrote:

Hi.

I'm one of the QIV developers.

Unfortunately I could not reproduce it here, but my photo archive is
only a tenth of his size. So if there is way for me to reproduce
the issue it would be much easier for me to help.

There are some issues in the report, which could perhaps be
clarified. Was qiv already up and showing a picture? Or
did he fire up qiv and went out while it was scanning the
mentioned 60000 pictures.

A SIGABRT could also be an indication for memory problems.
Is a dmesg output available, to check if qiv was not taken out by
the kernels OOM-killer? Also gdk_event_dispatch() is never
directly called from qiv. It is part of the gdk_main_loop(),
which makes it IMHO not so likely that qiv crash there.

Cheers,

 Thomas