GNOME Bugzilla – Bug 652300
Unhandled Exceptions in DatabaseTrackListModel.Reload(Hyena.Data.IListModel): NullReferenceException and System.IndexOutOfRangeException: Array index is out of range.
Last modified: 2011-06-12 10:23:54 UTC
Created attachment 189649 [details] Log of banshee --debug OS: Ubuntu 11.04 Playing songs with Banshee in the background, through Ubuntu's sound menu. Song finishes, Banshee is closed. A crash appears to have occured though no visual error massage is displayed. The seemingly relevant part of a "banshee --debug" log is attached.
What version of Mono? Can you consistently reproduce it?
According to Synaptic "mono-runtime" (and the other mono packages) indicate 2.6.7-5ubuntu3 as the version. I have had Banshee crash a number of times after a song has finished playing. This is the first time I've started Banshee in debug mode in an attempt to diagnose the problem, so I'm not sure *exactly* how to reproduce it. Over the next day or two I will try to pay closer attention to the exact situation leading up to the crash and post back.
OK, it happened again today. I couldn't isolate any particular test case, it just seems random. Attached is a second log file (banshee2.log) including at the bottom, output from the terminal that shows errors which weren't included in the debug log.
Created attachment 189709 [details] banshee2.log - Output from --debug as well as from terminal.
Awesome. The method where it fails is quite big so it's not clear what is the value which is null and shouldn't be. We would need you to install debug symbols of banshee (or if your distro doesn't provide them, that you compile your own copy of banshee from git and run it with 'make run'), so we can now the exact line number where it happens.
Created attachment 189755 [details] banshee2.log - Output from --debug and terminal with -dbg package installed This log contains the debug symbols. It seems gdb couldn't attach itself to Banshee as I wasn't running as root. Hopefully that wasn't required.
Thanks for the new log! It seems you're hitting a known problem with Mono 2.6.7. If you have a higher version of Mono than that one, or if you upgrade your mono and still see the issue, please reopen this bug: https://bugzilla.novell.com/show_bug.cgi?id=583817 Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 638257 ***