Ubuntu
banshee package

Banshee.exe crashed with SIGABRT in raise()

Bug #830041 reported by James Schriver on 2011-08-20

50

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	Banshee	New	Medium	gnome-bugs #656991
	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

See original description

Tags:

Revision history for this message

James Schriver (dashua) wrote on 2011-08-20:

#1

Dependencies.txt Edit (6.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (854 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (141 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (108.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (802 bytes, text/plain; charset="utf-8")
Registers.txt Edit (743 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (33.5 KiB, text/plain; charset="utf-8")

description:	updated
description:	updated
visibility:	private → public

Revision history for this message

Chow Loong Jin (hyperair) wrote on 2011-08-20:

#2

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 on 2011-08-20:

#3

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 on 2011-08-20:

#4

banshee_log Edit (38.1 KiB, text/plain)

Does this help?

Revision history for this message

James Schriver (dashua) wrote on 2011-08-20:

#5

banshee_log_1 Edit (138.3 KiB, text/plain)

Here's another log file following a crash.

Revision history for this message

Chow Loong Jin (hyperair) wrote on 2011-08-21:

#6

I've forwarded the log upstream, thanks!

Changed in banshee (Ubuntu):
status:	Incomplete → Triaged

Bug Watch Updater (bug-watch-updater) on 2011-08-21

Changed in banshee:
importance:	Unknown → Medium
status:	Unknown → New

Revision history for this message

Apport retracing service (apport) wrote on 2011-08-24:

#7

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 on 2011-08-24: Stacktrace.txt

#8

Stacktrace.txt Edit (5.3 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2011-08-24: ThreadStacktrace.txt

#9

ThreadStacktrace.txt Edit (95.9 KiB, text/plain)

Changed in banshee (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

gnome-bugs #656991
[UNCONFIRMED] Edit

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