Banshee.exe crashed with SIGABRT in raise()

Bug #830041 reported by James Schriver
50
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Banshee
New
Medium
banshee (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Banshee is periodically crashing consuming upwards of 350 % of the CPU as indicated by running top via command line. This occurs quite often bringing the OS to a crawl. I am often running killall banshee to restore my performance.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: banshee 2.1.0-1ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Sat Aug 20 08:23:52 2011
ExecutablePath: /usr/lib/banshee/Banshee.exe
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
InterpreterPath: /usr/bin/mono
ProcCmdline: banshee /usr/lib/banshee/Banshee.exe --redirect-log --play-enqueued
Signal: 6
SourcePackage: banshee
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 ?? ()
 ?? ()
Title: Banshee.exe crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
James Schriver (dashua) wrote :
description: updated
description: updated
visibility: private → public
Revision history for this message
Chow Loong Jin (hyperair) wrote :

The next time you encounter this issue, could you do "killall -SIGQUIT banshee" first before "killall banshee"? Then attach the ~/.config/banshee-1/log file to this bug report -- it should have a stack trace.

Revision history for this message
Chow Loong Jin (hyperair) wrote :

Oh yeah, don't forget to install banshee-dbg first.

Changed in banshee (Ubuntu):
status: New → Incomplete
Revision history for this message
James Schriver (dashua) wrote :

Does this help?

Revision history for this message
James Schriver (dashua) wrote :

Here's another log file following a crash.

Revision history for this message
Chow Loong Jin (hyperair) wrote :

I've forwarded the log upstream, thanks!

Changed in banshee (Ubuntu):
status: Incomplete → Triaged
Changed in banshee:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 mono_handle_native_sigsegv (signal=<optimized out>, ctx=<optimized out>) at mini-exceptions.c:2245
 <signal handler called>
 __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 __GI_abort () at abort.c:92
 monoeg_g_logv (log_domain=<optimized out>, log_level=<optimized out>, format=<optimized out>, args=<optimized out>) at goutput.c:134

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 banshee (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
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.