After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 420614 - crash in gThumb Image Viewer: Closed importer window d...
crash in gThumb Image Viewer: Closed importer window d...
Status: RESOLVED FIXED
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2007-03-20 17:19 UTC by Michael Chudobiak
Modified: 2007-03-26 13:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Michael Chudobiak 2007-03-20 17:19:55 UTC
What were you doing when the application crashed?
Closed importer window during driver initialization (before thumbnails start loading). I used Alt+F4 to close the window, because the driver initialization happens to quickly to click on the close-window "x".


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2925.fc6 #1 SMP Sat Mar 10 19:15:16 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 249847808 vsize: 0 resident: 249847808 share: 0 rss: 76906496 rss_rlim: 0
CPU usage: start_time: 1174411000 rtime: 0 utime: 600 stime: 0 cutime:561 cstime: 0 timeout: 39 it_real_value: 0 frequency: 13

Backtrace was generated from '/usr/bin/gthumb'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208572208 (LWP 24115)]
[New Thread -1276646512 (LWP 24131)]
[New Thread -1276118128 (LWP 24130)]
[New Thread -1274475632 (LWP 24129)]
[New Thread -1252967536 (LWP 24125)]
[New Thread -1252439152 (LWP 24124)]
0x00728402 in __kernel_vsyscall ()

Thread 1 (Thread -1208572208 (LWP 24115))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #3 <signal handler called>
  • #4 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #5 async_operation_step
    at dlg-photo-importer.c line 568
  • #6 g_source_get_current_time
    from /lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #8 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #10 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 main
    at main.c line 804
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
warning: the debug information found in "/usr/lib/debug//usr/lib/gnome-vfs-2.0/modules/libfile.so.debug" does not match "/usr/lib/gnome-vfs-2.0/modules/libfile.so" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-xpm.so" (CRC misma
warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-png.so" (CRC misma
warning: the debug information found in "/usr/lib/debug//usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so.debug" does not match "/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so" (CRC mis
Cannot access memory at address 0x1
Cannot access memory at address 0x1
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-03-20 17:21:34 UTC
This was a successful attempt to reproduce the bug reported at:

https://bugs.launchpad.net/ubuntu/+source/gthumb/+bug/93557

- Mike
Comment 2 manuel braga 2007-03-22 15:09:05 UTC
This one appears to be similar to previous, when the dialog is destroyed, it can still be alive a async_operation_step timeout with a pointer to the DialogData.
The segment fault ocorre at the first reference to "data".

When the destroy_cb is called, all timeouts must be stopped.
I don't have any camera at hand to be able to test. So this is a litle annoying for me to do a patch, without breaking things.
Comment 3 Paolo Bacchilega 2007-03-24 14:49:20 UTC
should be fixed in trunk now.
Comment 4 Michael Chudobiak 2007-03-26 13:27:53 UTC
Confirmed, marking as fixed.