GNOME Bugzilla – Bug 638257
Unexpected unmanaged Mono crash in DatabaseTrackListModel.Reload (Hyena.Data.IListModel)
Last modified: 2011-06-12 10:33:18 UTC
Created attachment 177182 [details] Crash log. Mono.Data.Sqlite.SqliteStatement doesn't implement interface Banshee.Collection.Database.IFilterListModel
Version of Mono? ( You can check by running ´mono --version´ in a console terminal. )
I'm running Mono 2.6.7
This looks a lot like this mono bug : https://bugzilla.novell.com/show_bug.cgi?id=583817 But if I'm reading it correctly, the fix should be in Mono 2.6.7, with this commit : https://github.com/mono/mono/commit/56f106393 Could you try to reproduce the problem with another version of Mono, 2.4.x or 2.8.x ?
This is on the changelog for 2.6.7. 583817 - SIGABRT (ERROR:mini-trampolines.c:183:mono_convert_imt_slot_to_vtable_slot: code should not be reached) using Saxon and the Ubuntu package probably in use does indeed build on a pristine 2.6.7 tarball though patched for various likely unrelated issues as by confirmation on #banshee <wolki> dnielsen: this is another one: http://pastebin.com/vGDtiD4U <dnielsen> wolki, that looks like a mono bug. mono --version? <wolki> if that one happens, i can even see the new metadata for artist and title appear in the main list, but they do not get saved Mono JIT compiler version 2.6.7 (Debian 2.6.7-3ubuntu1) So our users should have the fix in question.
Forgot to move this out of NEEDINFO
This could be related: https://bugzilla.gnome.org/show_bug.cgi?id=638988
<dnielsen> we have this mystery crasher in Banshee and it is indicated that it is a Mono but the fix in question should be in the Mono 2.6.7 packages. Anyone have any insights? https://bugzilla.gnome.org//show_bug.cgi?id=638257 <meebey> dnielsen: how often does that issue happen and is it reproducible in some way? <Laney> there's a minimal example on the upstrema bug you should try that <dnielsen> meebey, it seems very.. heisenbug like. I hate it when bugs do that, things should stay rightfully broken or work <meebey> hm, the fix was backported, I can see it in the 2.6.7 changelog * meebey compares the code to make sure <meebey> meebey@redbull:~/tmp/bug-583817$ mono BugTest.exe Success meebey@redbull:~/tmp/bug-583817$ So any other suspects?
Jasper, meebey would like to know if you are on x86 or amd64, also if you could paste the full output of mono --version it would be great. If you are using the Ubuntu/Debian packages, can you recall this happening with -3 (in which case meebey says this is unrelated to the suggested upstream mono problem. e.g. mono --version Mono JIT compiler version 2.6.7 (Debian 2.6.7-4) Copyright (C) 2002-2010 Novell, Inc and Contributors. www.mono-project.com TLS: __thread GC: Included Boehm (with typed GC and Parallel Mark) SIGSEGV: altstack Notifications: epoll Architecture: amd64 Disabled: none
Mono JIT compiler version 2.6.7 (Debian 2.6.7-3ubuntu1) Copyright (C) 2002-2010 Novell, Inc and Contributors. www.mono-project.com TLS: __thread GC: Included Boehm (with typed GC and Parallel Mark) SIGSEGV: altstack Notifications: epoll Architecture: amd64 Disabled: none Whether I had -3 back then depends on if the package was released by the time th e bug was filed... I upgrade every day.
<meebey> dnielsen: any idea how many people are hitting that missing interface crasher thing? <meebey> I have seen it for the first time <meebey> dnielsen: but nontheless, it is for sure a mono bug.. the report should be moved upstream <meebey> I doubt the class really missing to implement the interface, it would work for nobody then <dnielsen> meebey, in terms of solid reports with traces, Jasper and I think I had it the other day. It seems hard to trigger but definitely not a single machine issue <meebey> at Banshee.SmartPlaylist.SmartPlaylistSource.RefreshAndReload () <0x0001e> at Banshee.SmartPlaylist.SmartPlaylistSource.HandleTracksChanged (Banshee.Sources.Source,Banshee.Sources.TrackEventArgs) <0x000bb> some kind of playlist refresh thing I wonder how often that gets triggered as thats where it happened <dnielsen> it sounds like it would be commonly used. Time to read some code I suspect
Please file with Mono, this is not a Banshee/GNOME bug. It's possible/likely this isn't an issue in recent Banshee since we rewrote our database layer to not use Mono.Data.Sqlite.
(In reply to comment #11) > Please file with Mono, this is not a Banshee/GNOME bug. The bug seems to be https://bugzilla.novell.com/show_bug.cgi?id=583817 . There, it says it has been backported, but it's not clear what is the version of mono it was backported to. Most likely the fix is in 2.8.x or 2.10.x series. If anyone hits the bug again with those version, please reopen the Mono bug. (In reply to comment #11) > Please file with Mono, this is not a Banshee/GNOME bug. It's possible/likely > this isn't an issue in recent Banshee since we rewrote our database layer to > not use Mono.Data.Sqlite. Unfortunately it's still an issue because I just found a duplicate (bug 652300) that has just been filed against v2.1.0 :(
*** Bug 652300 has been marked as a duplicate of this bug. ***
*** Bug 638988 has been marked as a duplicate of this bug. ***
*** Bug 651512 has been marked as a duplicate of this bug. ***
*** Bug 649341 has been marked as a duplicate of this bug. ***