eog crashed with SIGSEGV in gtk_tree_model_get_valist()

Bug #1244071 reported by Serhiy
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
eog (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

I was saving the hardware poster from cheat-sheets.org and immediately tried to open it with eog.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: eog 3.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
Uname: Linux 3.8.0-32-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
Date: Thu Oct 24 09:24:38 2013
ExecutablePath: /usr/bin/eog
MarkForUpload: True
ProcCmdline: /usr/bin/eog /media/i/data/uni/Computer_hardware_poster_1_7_by_Sonic840.png.part
SegvAnalysis:
 Segfault happened at: 0xb721ac3d <gtk_tree_model_get_valist+285>: mov 0x18(%eax),%esi
 PC (0xb721ac3d) ok
 source "0x18(%eax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: eog
StacktraceTop:
 gtk_tree_model_get_valist () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 gtk_tree_model_get () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 eog_list_store_thumbnail_set ()
 ?? ()
 ?? ()
Title: eog crashed with SIGSEGV in gtk_tree_model_get_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video

Revision history for this message
Serhiy (xintx-ua) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_tree_model_get_valist (tree_model=tree_model@entry=0xa0786b0, iter=iter@entry=0xbf9cd100, var_args=0xbf9cd0bc "\334\320\234\277\377\377\377\377", var_args@entry=0xbf9cd0b8 "\001") at /build/buildd/gtk+3.0-3.6.4/./gtk/gtktreemodel.c:1765
 gtk_tree_model_get (tree_model=0xa0786b0, iter=iter@entry=0xbf9cd100) at /build/buildd/gtk+3.0-3.6.4/./gtk/gtktreemodel.c:1727
 eog_list_store_thumbnail_set (store=0xa0786b0, iter=iter@entry=0xbf9cd100) at eog-list-store.c:872
 image_thumb_changed_cb (image=image@entry=0xa0d41f8, data=data@entry=0x9ff8050) at eog-window.c:806
 eog_window_display_image (window=window@entry=0x9ff8050, image=0xa0d41f8) at eog-window.c:901

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in eog (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Serhiy (xintx-ua)
information type: Private → Public
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in eog (Ubuntu):
status: New → Triaged
Revision history for this message
Cebtenzzre (cebtenzzre) wrote :

I'm getting a similar crash. Here's the backtrace:

#0 0x00007ffff75ee129 in gtk_tree_model_get_valist () at /usr/lib/libgtk-3.so.0
#1 0x00007ffff75ee450 in gtk_tree_model_get () at /usr/lib/libgtk-3.so.0
#2 0x00007ffff7d4b1ca in () at /usr/lib/eog/libeog.so
#3 0x00007ffff7d4f76a in () at /usr/lib/eog/libeog.so
#4 0x00007ffff58556d0 in ffi_call_unix64 () at /usr/lib/libffi.so.6
#5 0x00007ffff58550a0 in ffi_call () at /usr/lib/libffi.so.6
#6 0x00007ffff7ceae48 in g_cclosure_marshal_generic_va () at /usr/lib/libgobject-2.0.so.0
#7 0x00007ffff7cd216e in g_signal_emit_valist () at /usr/lib/libgobject-2.0.so.0
#8 0x00007ffff7cd2a80 in g_signal_emit () at /usr/lib/libgobject-2.0.so.0
#9 0x00007ffff7a2d8ba in () at /usr/lib/libgio-2.0.so.0
#10 0x00007ffff7bf9a2f in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#11 0x00007ffff7bfb5e9 in () at /usr/lib/libglib-2.0.so.0
#12 0x00007ffff7bfb62e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#13 0x00007ffff7a8593e in g_application_run () at /usr/lib/libgio-2.0.so.0
#14 0x000055555555518f in main ()

I'm on Arch Linux, using eog version 3.28.4. This only happens to me when opening a large file on a slow disk.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.