Banshee consuming 100% CPU after quitting

Bug #853656 reported by Alex Peters
This bug report is a duplicate of:  Bug #854845: Banshee.exe crashes a lot. Edit Remove
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I double-clicked an MP3 file to play it. Banshee opened. Preferring to play the file with Totem, I closed Banshee.

90 minutes later, top reports that Banshee never actually quit and has in fact been consuming near 100% CPU in the interim.

strace on the process says that Banshee is doing this repeatedly:

futex(0xe657c4, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 107807, {1316410606, 586000000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
futex(0xe65798, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0xe657c4, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 107809, {1316410606, 686000000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
futex(0xe65798, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0xe657c4, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 107811, {1316410606, 786000000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
futex(0xe65798, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0xe657c4, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 107813, {1316410606, 886000000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
futex(0xe65798, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0xe657c4, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 107815, {1316410606, 986000000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
futex(0xe65798, FUTEX_WAKE_PRIVATE, 1) = 0

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: banshee 2.1.4-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Mon Sep 19 15:33:42 2011
ExecutablePath: /usr/lib/banshee/Banshee.exe
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/mono
SourcePackage: banshee
UpgradeStatus: Upgraded to oneiric on 2011-09-12 (6 days ago)

Revision history for this message
Alex Peters (alex-peters) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

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