GNOME Bugzilla – Bug 471093
Banshee locks up your system when you delete your library
Last modified: 2008-03-11 16:14:56 UTC
This is a pretty simple bug. If I start playing music and then delete the contents of my library at the same time, Banshee will keep trying to play the next track, while the next track will be removed from the collection at the same time. To reproduce: Open your collection (it should have a lot of songs stored if this should really work and make you entire computer freeze.. mine did) Start playing a song... lets say number 20-something in your collection (of 500+ songs). Now press ctrl-a to select all songs, right click and choose 'remove'. Watch what happens when the song that's playing gets removed... Solution: If a song that's playing is removed from the collection, then DON'T play the next song on the playlist.
I'd rather not see the solution you express. What if I really only removed one song and I want it to move on? It would be nice if it moved to the next song on the playlist unless told otherwise. Granted, it shouldn't crash your machine. I've not been successful in duplicating this problem. Does it happen every time for you? We'll need a backtrace to get an idea of what is actually going on. Maybe you could get this using a smaller playlist since it sounds like it only crashes on large lists. Information an getting more out of your crash can be found here: http://banshee-project.org/Debugging
I think you may have missed my point: If I remove the song that's playing or a selection of songs, and one of them is playing, then *I* would actually expect playback to stop. I'm removing the song that's playing... that's a little more aggressive than just pressing stop, if you know what I mean. I'm not gonna reproduce this. I'm sure it will happen again the next time I try to delete my whole library while playing, and the only thing that happens is that Banshee will start-stop every song in my library until memory/cpu is totally exhausted. But I get your point, I just think that the solution for your problem would be to simply move on to the next song before removing the song that's playing. Otherwise a more complex solution should be made, e.g. where Banshee halts playback once it removes the second song that's played.. as a simple precaution. And please remember, that the severity of this bug, is so high that it brings down a whole system. Mine became 100% unresponsive - even when pinging the machine.
So this only happened when deleting all the songs in the current playlist, not just one or maybe twenty songs?
I don't think my computer will actually freeze if I only remove a few concurrent songs (and one of them is playing). The freeze happened after Banshee played snippets of like 50+ songs that it was playing while removing them and being 99% unresponsive. I can probably confirm this pretty quickly once I get home. I can also try and setup a new user account with a gigantic library and removing it while playing and doing a trace... just don't know if I'll ever see the results of the trace.
I also have this same error, I wanted to delete all my library to start again, system was working but locked up, after 30min still "running" I killed it. I can Confirm this bug as a issue. My Asus laptop fans start going full ( full CPU) usage.
Scott, thanks for the confirmation. If you want to get rid of your library in the future it would be cleaner to rm ~/.config/banshee.db as that will really wipe it out much more quickly and prompt Banshee to re-create it.
Is this a duplicate of bug #469393?
Just to clarify it: The issue I was referring to was that when playing songs AND deleting the library, Banshee would crash. The other bug seems to be describing a different scenario.
Can we get some output from 'banshee --debug' or something else to go on?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!