Banshee.exe crashed with SIGSEGV

Bug #1049352 reported by Laurent Bonnaud
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mono (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I was trying to import a bunch of MP3 files into banshee.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: banshee 2.4.1-3ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
Uname: Linux 3.5.0-14-generic i686
ApportVersion: 2.5.1-0ubuntu7
Architecture: i386
Date: Tue Sep 11 22:15:33 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/banshee/Banshee.exe
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee /usr/lib/banshee/Banshee.exe
SegvAnalysis:
 Segfault happened at: 0xb7794f0c <_dl_tls_get_addr_soft+60>: mov (%ecx,%edx,8),%eax
 PC (0xb7794f0c) ok
 source "(%ecx,%edx,8)" (0x649afee8) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: banshee
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: Banshee.exe crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2011-09-06 (371 days ago)
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm libvirtd lpadmin plugdev pulse pulse-access scanner staff video

Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 runtime_invoke_signature_equal (sig1=0x3ea, sig2=0xb4c94420) at marshal.c:4196
 monoeg_g_hash_table_lookup_extended (hash=hash@entry=0x9bc58e8, key=key@entry=0xb4c94420, orig_key=orig_key@entry=0xa14cd9a8, value=value@entry=0xa14cd9ac) at ghashtable.c:300
 monoeg_g_hash_table_lookup (hash=0x9bc58e8, key=0xb4c94420) at ghashtable.c:280
 mono_marshal_get_runtime_invoke (method=method@entry=0x9bc4a1c, virtual=virtual@entry=0) at marshal.c:4583
 mono_jit_runtime_invoke (method=0x9bc4a1c, obj=0x300e70, params=0x0, exc=0x0) at mini.c:5612

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 banshee (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Chow Loong Jin (hyperair) wrote :

This looks like a mono bug. Reassigning.

affects: banshee (Ubuntu) → mono (Ubuntu)
Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :

People trying to reproduce this bug should note that I use those environment variables:

MALLOC_PERTURB_=117
MALLOC_CHECK_=3

that have an impact on memory allocation and may reveal latent memory corruptions that remain silent otherwise.

Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :

I cannot reproduce this bug any longer, therefore I am closing it.

Changed in mono (Ubuntu):
status: New → 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.