banshee interface becomes unresponsive while playing radio stream

[Martin Pool]

When I play an m3u radio stream in banshee, the main window becomes grey, blank and unresponsive, although the music continues to play. strace shows continuous loop of

futex(0x1b1358c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 33407, {1312952124, 741000000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
futex(0x1b13560, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x8e9538, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x8e9538, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x1b1358c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 33409, {1312952124, 841000000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
futex(0x1b13560, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x8e9538, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x8e9538, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x8e9538, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x8e9538, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x8e9538, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x1b1358c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 33411, {1312952124, 942000000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
futex(0x1b13560, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x8e9538, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x1b1358c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 33413, {1312952125, 42000000}, ffffffff^C <unfinished ...>
Process 17978 detached

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: banshee 2.1.0-1ubuntu5
ProcVersionSignature: Ubuntu 3.0.0-8.10-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
Date: Wed Aug 10 14:55:43 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/banshee/Banshee.exe
InterpreterPath: /usr/bin/mono
ProcEnviron:
 SHELL=/bin/zsh
 LANG=en_AU.UTF-8
SourcePackage: banshee
UpgradeStatus: Upgraded to oneiric on 2011-08-04 (6 days ago)

[Chow Loong Jin (hyperair)]

On 10/08/2011 12:58, Martin Pool wrote:
> Public bug reported:
>
> When I play an m3u radio stream in banshee, the main window becomes
> grey, blank and unresponsive, although the music continues to play.
> strace shows continuous loop of
> [...]

It's probably a deadlock of sorts. Could you get the output from "banshee
--debug", and when it hangs, run "killall -SIGQUIT banshee". That should dump a
whole bunch of stack traces to the terminal (one of each thread).

Please install "banshee-dbg" before doing this, so we get more information in
the stack traces.

  status incomplete

--
Kind regards,
Loong Jin

[Martin Pool (mbp)]

  status confirmed

banshee --debug crashes as follows, without hanging:

Exception has been thrown by the target of an invocation.

An unhandled exception was thrown: Could not read add-in description

  at Mono.Addins.Addin.get_Description () [0x00000] in <filename unknown>:0
  at Mono.Addins.TreeNode.ResetCachedData () [0x00000] in <filename unknown>:0
  at Mono.Addins.TreeNode.ResetCachedData () [0x00000] in <filename unknown>:0
  at Mono.Addins.TreeNode.ResetCachedData () [0x00000] in <filename unknown>:0
  at Mono.Addins.TreeNode.ResetCachedData () [0x00000] in <filename unknown>:0
  at Mono.Addins.ExtensionContext.ResetCachedData () [0x00000] in
<filename unknown>:0
  at Mono.Addins.AddinEngine.ResetCachedData () [0x00000] in <filename
unknown>:0
  at Mono.Addins.Database.AddinDatabase.ResetCachedData () [0x00000]
in <filename unknown>:0
  at Mono.Addins.Database.AddinDatabase.Update (IProgressStatus
monitor, System.String domain) [0x00000] in <filename unknown>:0
  at Mono.Addins.Database.AddinDatabase.Repair (IProgressStatus
monitor, System.String domain) [0x00000] in <filename unknown>:0
  at Mono.Addins.AddinRegistry.Rebuild (IProgressStatus monitor)
[0x00000] in <filename unknown>:0
  at Banshee.ServiceStack.ServiceManager.InitializeAddins () [0x00075]
in /build/buildd/banshee-2.1.0/src/Core/Banshee.Services/Banshee.ServiceStack/ServiceManager.cs:86
  at Banshee.ServiceStack.ServiceManager.DefaultInitialize ()
[0x00005] in /build/buildd/banshee-2.1.0/src/Core/Banshee.Services/Banshee.ServiceStack/ServiceManager.cs:119
  at Banshee.ServiceStack.Application.Initialize () [0x00000] in
/build/buildd/banshee-2.1.0/src/Core/Banshee.Services/Banshee.ServiceStack/Application.cs:80
  at Banshee.Gui.GtkBaseClient.Initialize (Boolean
registerCommonServices) [0x00010] in
/build/buildd/banshee-2.1.0/src/Core/Banshee.ThickClient/Banshee.Gui/GtkBaseClient.cs:143
  at Banshee.Gui.GtkBaseClient..ctor (Boolean initializeDefault,
System.String defaultIconName) [0x00013] in
/build/buildd/banshee-2.1.0/src/Core/Banshee.ThickClient/Banshee.Gui/GtkBaseClient.cs:95
  at Banshee.Gui.GtkBaseClient..ctor () [0x00000] in <filename unknown>:0
  at Nereid.Client..ctor () [0x00000] in <filename unknown>:0
  at (wrapper managed-to-native)
System.Reflection.MonoCMethod:InternalInvoke
(System.Reflection.MonoCMethod,object,object[],System.Exception&)
  at System.Reflection.MonoCMethod.Invoke (System.Object obj,
BindingFlags invokeAttr, System.Reflection.Binder binder,
System.Object[] parameters, System.Globalization.CultureInfo culture)
[0x00000] in <filename unknown>:0
Exception has been thrown by the target of an invocation.

  at System.Reflection.MonoCMethod.Invoke (System.Object obj,
BindingFlags invokeAttr, System.Reflection.Binder binder,
System.Object[] parameters, System.Globalization.CultureInfo culture)
[0x00000] in <filename unknown>:0
  at System.Reflection.MonoCMethod.Invoke (BindingFlags invokeAttr,
System.Reflection.Binder binder, System.Object[] parameters,
System.Globalization.CultureInfo culture) [0x00000] in <filename
unknown>:0
  at System.Reflection.ConstructorInfo.Invoke (System.Object[]
parameters) [0x00000] in <filename unknown>:0
  at Syst...

[Chow Loong Jin (hyperair)]

That trace looks like it comes from the mono-addins bug that causes it to crash
when mono is ran with --debug. I'll see if we can backport the fix from Oneiric
so we can get a proper crash report.

  status incomplete

--
Kind regards,
Loong Jin

[Martin Pool (mbp)]

I'll see if I can get the sigquit tracebacks, but of course now that
it's being watched, it's not going to fail.

Martin

[Chow Loong Jin (hyperair)]

On 10/08/2011 15:15, Martin Pool wrote:
> I'll see if I can get the sigquit tracebacks, but of course now that
> it's being watched, it's not going to fail.

Haha, I can totally relate. Banshee has a --redirect-log in its .desktop file,
which dumps stuff into ~/.config/banshee-1/log, so you could just look into that
file after SIGQUIT-ing, if you didn't start Banshee in a terminal. :-)

--
Kind regards,
Loong Jin

[Chow Loong Jin (hyperair)]

This is weird. I just installed Banshee on my Oneiric chroot, and didn't notice
the mono-addins crash. It looks like you're also running on Oneiric, so you
shouldn't have this crash. =\

--
Kind regards,
Loong Jin

[Martin Pool (mbp)]

I ran it again with --debug and this time it worked.

[Chow Loong Jin (hyperair)]

On 11/08/2011 10:25, Martin Pool wrote:
> I ran it again with --debug and this time it worked.
>
> ** Attachment added: "startup.log"
> https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/823723/+attachment/2267339/+files/startup.log
>

Alright. Could you -SIGQUIT it when it hangs again then, please? This time with
--debug on. :-)

--
Kind regards,
Loong Jin

[Launchpad Janitor (janitor)]

[Expired for banshee (Ubuntu) because there has been no activity for 60 days.]