[Mono-bugs] [Bug 384294] Crash preceded by "Thread (nil) may have been prematurely finalized"

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Thu Sep 4 14:54:13 EDT 2008


User avidigal at novell.com added comment

Andreia Gaita <avidigal at novell.com> changed:

           What    |Removed                                         |Added
             Status|NEW                                             |NEEDINFO
      Info Provider|                                                |martin_costello at talk21.com

--- Comment #12 from Andreia Gaita <avidigal at novell.com>  2008-09-04 12:54:12 MDT ---
So, this appears to be happening on one of two situations:

1) gluezilla was built against xulrunner 1.8, but gets executed with xulrunner
1.9 (or vice-versa)

2) xulrunner is loading components from it's cache without checking whether
they are the right ones (yes, it does this, and no, it doesn't complain, just
loads them blindly). when it actually tries to load the component (as in, tries
to actually initialize the browser), it crashes. the components can be wrong in
the cache if you've ran an application that uses a gluezilla built with 1.8
(like the one your system ships), and then you try to run an svn version built
with 1.9.

On svn and the latest mono-2.0 tag, issue 1) is fixed by forcing a specific
runtime version. If gluezilla was built with 1.8, it will not try to load 1.9
even if it is the only one present.

Issue 2) is being sorted out and hopefully will land before the release. In the
meantime, the cache files are kept in ~/.local/share/.mono/mozilla, so you can
delete that mozilla directory to clean out the cache and try again.

Please let me know whether one of these solutions fixes it for you. There might
be the possibility that your distro (excluding suse and ubuntu that I know of)
might be patching xulrunner to such an extent that it makes it unstable when
gluezilla tries to use it :P

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the mono-bugs mailing list