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 486886 - crash in gThumb Image Viewer: Opening an image in the ...
crash in gThumb Image Viewer: Opening an image in the ...
Status: RESOLVED FIXED
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
: 494838 510603 510605 521146 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-10-15 17:15 UTC by Paul-Erik Törrönen
Modified: 2008-03-10 12:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Paul-Erik Törrönen 2007-10-15 17:15:41 UTC 
What were you doing when the application crashed?
Opening an image in the filebrowser. The dir contained several other images in both jpg and nef (Nikon RAW) format


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 78807040 vsize: 78807040 resident: 43368448 share: 20238336 rss: 43368448 rss_rlim: 4294967295
CPU usage: start_time: 1192468461 rtime: 87 utime: 78 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208924448 (LWP 5420)]
[New Thread -1238209648 (LWP 5430)]
[New Thread -1237681264 (LWP 5429)]
[New Thread -1237152880 (LWP 5428)]
[New Thread -1226134640 (LWP 5426)]
[New Thread -1225606256 (LWP 5425)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 170376

Thread 1 (Thread -1208924448 (LWP 5420))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
    from /usr/lib/gthumb/libgthumb.so
  • #5 get_metadata_time
    from /usr/lib/gthumb/libgthumb.so
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #11 ??
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #14 ??
    from /usr/lib/gthumb/libgthumb.so
  • #15 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #20 image_loader_load_from_image_loader
    from /usr/lib/gthumb/libgthumb.so
  • #21 load_from_image_loader__step2
    from /usr/lib/gthumb/libgthumb.so
  • #22 ??
    from /usr/lib/gthumb/libgthumb.so
  • #23 ??
    from /lib/libglib-2.0.so.0
  • #24 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #25 ??
    from /lib/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #27 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-10-15 17:22:30 UTC 
Are you using version 2.10.6?

I suspect that one particular image is causing the crash. Could you email the image that causes this to mjc@avtechpulse.com for analysis?

- Mike
Comment 2 Paul-Erik Törrönen 2007-10-15 19:23:44 UTC 
(In reply to comment #1)
> Are you using version 2.10.6?

2.10.6-1.fc7 (i386) to be precise.

> I suspect that one particular image is causing the crash. Could you email the
> image that causes this to mjc@avtechpulse.com for analysis?

Yes, once I find that pic, there are about 286 images in the dir which I tried to browse, so it will take a while. Forgot to mention that in addition to the jpeg's and nef's, there are also a couple of mrw's (Minorta RAW).

I'll email the offending file once I have it located. Just as a warning, the files are between 2-12MB in size,
Comment 3 Michael Chudobiak 2007-10-15 20:27:34 UTC 
Thank you for the emailed sample image. Crash confirmed with 2.10.7:

+ Trace 170418

  • #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 gth_minimal_exif_tag_action
    at gth-exif-utils.c line 447
  • #5 get_metadata_time
    at gth-exif-utils.c line 194
  • #6 window_update_statusbar_image_info
    at gth-browser.c line 478 

- Mike
Comment 4 Michael Chudobiak 2007-10-15 23:51:17 UTC 
The sample image was a bit unusual because it had no IFD1.

There was a bug that caused an offset pointer to overflow if no IFD1 was found. I've fixed that as of svn rev 2023.

The fix should appear in gthumb 2.10.8.

- Mike
Comment 5 Michael Chudobiak 2008-03-10 12:29:48 UTC 
*** Bug 521146 has been marked as a duplicate of this bug. ***
Comment 6 Michael Chudobiak 2008-03-10 12:31:57 UTC 
*** Bug 494838 has been marked as a duplicate of this bug. ***
Comment 7 Michael Chudobiak 2008-03-10 12:34:17 UTC 
*** Bug 510603 has been marked as a duplicate of this bug. ***
Comment 8 Michael Chudobiak 2008-03-10 12:34:36 UTC 
*** Bug 510605 has been marked as a duplicate of this bug. ***