GNOME Bugzilla – Bug 419330
Banshee freezes after a period of time
Last modified: 2008-02-06 03:28:29 UTC
Sorry for the ambiguous summary, but I'm not sure what's going on here. I'll leave Banshee playing and then I'll find that my music stopped. Turns out my CPU is churning away and/or my RAM is being hogged by Banshee. I can force quit it and restart, but why is this happening? I'm not sure exactly how to pinpoint the problem, but here's what info I can provide off the top of my head. Valgrind log and debug output to follow. I could also host my banshee.db if it would help.
Created attachment 84765 [details] Debug output Debug output from running instance of Banshee
Created attachment 84766 [details] Valgrind log
Created attachment 85057 [details] Thread dump created with Ctrl-\ Ironically, I just finished reading the mailing list thread about this bug, remembering the few times I've seen this myself, when lo and behold it happens again. I'm on Fedora Core 6, running the latest SVN banshee. I've also seen the same thing happen when I was inporting large numbers of songs (6000+), but it eventually recovered if I waited long enough. Checking lsof during those periods would first show that banshee had an mp3 open and was then talking (oddly enough) to various w3.org servers.
Created attachment 87049 [details] crash dump I have the same thing happen. My dump is a little different than Joseph's. To get this, I run banshee --debug from a terminal, wait for it to crash (usually a couple hours) then run kill -QUIT PID. I got this same trace twice now (problem in QueuedSqlite triggered by SmartPlaylist's RefreshMembers) but Joseph's trigger seems to be different, but same net result, a crash in QueuedSqlite.
Bumping to high priority. This happens to me regularly, every couple hours.
Is this still an issue with anyone? I haven't had this problem lately.
Closing this bug report as no further information has been provided. Hopefully that means something along the way fixed it! Please feel free to reopen this bug if you can produce this bug again.