nautilus crashed with SIGSEGV in malloc()

Bug #420093 reported by Roman Horník
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Confirmed
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: brasero

ProblemType: Crash
Architecture: i386
Date: Thu Aug 27 20:22:41 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
NonfreeKernelModules: nvidia
Package: libbrasero-media0 2.27.91-0ubuntu1
ProcCmdline: nautilus /var/log
ProcEnviron:
 PATH=(custom, no user)
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-7.27-generic
SegvAnalysis:
 Segfault happened at: 0x1a0c1ef: mov 0x4(%edi),%edx
 PC (0x01a0c1ef) ok
 source "0x4(%edi)" (0x0a9a9eac) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: brasero
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 malloc () from /lib/tls/i686/cmov/libc.so.6
 g_malloc () from /usr/lib/libglib-2.0.so.0
 g_memdup () from /usr/lib/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in malloc()
Uname: Linux 2.6.31-7-generic i686
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape vboxusers video

Revision history for this message
Roman Horník (roman.hornik) wrote :
Martin Pitt (pitti)
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in brasero (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

valgrind log obtained by running:

G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log gksu nautilus

Although, it might just be getting info on gksu, not what we really want to look at... Dropping to to root and running just Nautilus doesn't seem to reproduce the crash though...

Probably related:

Bug #420841
Bug #419565
Bug #419092

Changed in brasero (Ubuntu):
status: Incomplete → Confirmed
Martin Pitt (pitti)
tags: added: need-i386-retrace
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:malloc_consolidate (av=<value optimized out>)
_int_malloc (av=<value optimized out>,
*__GI___libc_malloc (bytes=502) at malloc.c:3663
IA__g_malloc (n_bytes=502)
IA__g_memdup (mem=0xb65c0f80, byte_size=502)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
tags: removed: need-i386-retrace
Martin Pitt (pitti)
visibility: private → public
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.