eog crashed with SIGSEGV in malloc_consolidate()

Bug #730733 reported by Brian Murray
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mago
Fix Released
Undecided
Patrick Wright
eog (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: eog

Whenever I use eog with the map plugin enabled (Edit -> Preferences, Plug-ins tab, check Map) eog crashes on closing it.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: eog 2.32.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
Architecture: amd64
CheckboxSubmission: fee5e196cb921cbd36888f428b38b488
CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32
CrashCounter: 1
Date: Mon Mar 7 08:48:28 2011
ExecutablePath: /usr/bin/eog
ProcCmdline: eog /var/log/bootchart/hostname-natty-20110307-1.png
ProcEnviron:
 SHELL=/bin/zsh
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
 PATH=(custom, user)
SegvAnalysis:
 Segfault happened at: 0x7f7d5c2d2def <malloc_consolidate+271>: mov 0x8(%r12),%r15
 PC (0x7f7d5c2d2def) ok
 source "0x8(%r12)" (0x7f7d5e4842e0) in non-readable VMA region: 0x7f7d5e2dc000-0x7f7d5e4db000 ---p /usr/lib/libgio-2.0.so.0.2800.1
 destination "%r15" ok
SegvReason: reading VMA /usr/lib/libgio-2.0.so.0.2800.1
Signal: 11
SourcePackage: eog
StacktraceTop:
 malloc_consolidate (av=0x7f7d5c5fc1c0) at malloc.c:5155
 _int_malloc (av=0x7f7d5c5fc1c0, bytes=8192) at malloc.c:4373
 __libc_malloc (bytes=8192) at malloc.c:3660
 g_realloc (mem=<value optimized out>, n_bytes=8192) at /build/buildd/glib2.0-2.28.1/./glib/gmem.c:233
 g_string_maybe_expand (string=0x1f34b20, len=<value optimized out>) at /build/buildd/glib2.0-2.28.1/./glib/gstring.c:401
Title: eog crashed with SIGSEGV in malloc_consolidate()
UpgradeStatus: Upgraded to natty on 2011-03-01 (6 days ago)
UserGroups: adm admin audio cdrom dialout dip family floppy fuse libvirtd lpadmin plugdev pulse pulse-access sambashare sbuild scanner video

Revision history for this message
Brian Murray (brian-murray) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 malloc_consolidate (av=0x7f7d5c5fc1c0) at malloc.c:5161
 __malloc_assert (av=0x7f7d5c5fc1c0, bytes=<value optimized out>) at malloc.c:351
 sYSMALLOc (av=0x7f7d5c5fc1c0, bytes=<value optimized out>) at malloc.c:3099
 _int_malloc (av=0x7f7d5c5fc1c0, bytes=<value optimized out>) at malloc.c:4747
 malloc_atfork (sz=140176397418944, caller=<value optimized out>) at arena.c:218

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in eog (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Patrick Wright (patrickmwright) wrote :

Brian,
I have been unable to replicate this bug. eog does not crash after enabling Map, closing the prefs window, then closing eog.

Changed in mago:
assignee: nobody → Patrick Wright (patrickmwright)
status: New → In Progress
Revision history for this message
Patrick Wright (patrickmwright) wrote :

a mago regression test has been created

Changed in mago:
status: In Progress → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote :

Setting to Confirmed since it must have been recreated.

Changed in eog (Ubuntu):
status: New → Confirmed
Revision history for this message
Muelli (ubuntu-bugs-auftrags-killer) wrote :

I seem to be able to reproduce this issue easily. Just open eog with a set of enabled plugins (Date in statusbar, Exif display, Map, Reload image, Zoom to fit width) and close eog. It crashes.

With no plugins enabled, it doesn't crash.

With only the map plugin enabled, it crashes with the procedure mentioned above.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I'm closing this report. It is fixed in the latest development release Oneiric.

Changed in eog (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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