Bug 230773

Summary:	dynamic playlist stops updating because of biassolver hanging
Product:	[Applications] amarok	Reporter:	Heinz Wiesinger <pprkut>
Component:	Playlists/Dynamic Playlists	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	lfranchi
Priority:	NOR
Version:	2.3-GIT
Target Milestone:	---
Platform:	Slackware
OS:	Unspecified
Latest Commit:		Version Fixed In:	2.4.0
Sentry Crash Report:
Attachments:	log file of "amarok -nofork -debug" Output of "amarok -debug -nofork"

Description Heinz Wiesinger 2010-03-14 22:44:31 UTC

Version:           2.3-git_a2ce050 (using KDE 4.4.1)
Installed from:    Slackware Packages

amarok stops updating the dynamic playlist after some songs. The progress bar indicating the status of "Generating playlist..." is stuck at 23% and no songs are added to the playlist anymore. Also quitting amarok leaves an amarok process running in the background which indicates that the biassolver is truely stuck somewhere.

Comment 1 Heinz Wiesinger 2010-03-14 22:45:37 UTC

Created attachment 41637 [details]
log file of "amarok -nofork -debug"

Comment 2 Myriam Schweingruber 2010-03-15 01:18:43 UTC

Thank you for the output, but it contains a lot of data irrelevant to this report. Could you pleas try to reproduce it by actually only generate a dynamic playlist and exit once it gets stuck? It's rather hard to find the relevant part in more than 13.000 lines of output.

Comment 3 Heinz Wiesinger 2010-03-15 07:50:58 UTC

Well, that's what I did for this log :/
The playlist was already present when starting up amarok. But apart from that all I did was hitting the play button, wait for the playList generation to get stuck and then wait for the song to finish to quit amarok.
The behaviour is unfortunately rather erratic. It can happen after 1-2 songs, and then again it worked just fine for hours without getting stuck.
I can try again today but I doubt I'll be able to produce anything shorter than already present here.

Comment 4 Heinz Wiesinger 2010-03-15 15:31:45 UTC

Created attachment 41666 [details]
Output of "amarok -debug -nofork"

Ok, I got a smaller log file. This time I started to play a song but paused it after a few seconds and then waited for the biassolver to hang.
I seriously doubt I will get anything smaller than this, so this is as good as I can do :-/
But if you know a way to get more specific debugging output I'll be happy to provide that.

Comment 5 Myriam Schweingruber 2010-03-16 02:23:03 UTC

(In reply to comment #4)
> Created an attachment (id=41666) [details]
> Output of "amarok -debug -nofork"
> 
> Ok, I got a smaller log file. This time I started to play a song but paused it
> after a few seconds and then waited for the biassolver to hang.
> I seriously doubt I will get anything smaller than this, so this is as good as
> I can do :-/
> But if you know a way to get more specific debugging output I'll be happy to
> provide that.

Perfect, thanks a bunch, 4000 something lines are easier to see through than 13.000. But you are right, I doubt there is any way to get this shorter, indeed.

Comment 6 Myriam Schweingruber 2011-05-07 11:30:29 UTC

Could you please upgrade to a newer Amarok version and test again? Current is Amarok 2.4.0, Amarok 2.4.1 is to be released tomorrow.

Please report back.

Comment 7 Heinz Wiesinger 2011-05-08 15:51:23 UTC

Works fine for me now in 2.4.0

Comment 8 Myriam Schweingruber 2011-05-10 02:46:44 UTC

Thank you for the fast feedback.