[Moonlight-list] Firefox removing XPCOM for FF 3.6a1

Brad Taylor brad at getcoded.net
Tue Oct 6 14:35:12 EDT 2009


Hey,

> Recently, I started encountering segfaults in the moon-unit tests.
> Originally, I attributed the crashes to instability caused by the
> mono-2-6 move, but I finally got a chance to find the cause today.
> 
> The segfault I was getting was at http://paste2.org/p/448706.  It seems
> that in ff3-dom.cpp:182, Firefox is setting item to nsnull, causing the
> actual segfault later on.
> 
> As I've been (epically) working on a Firefox patch myself, I've been
> tracking the latest FF 3.6 branch.  It seems that in FF 3.6a1, they have
> deprecated the XPCOM interface, causing any calls to NPN_GetValue with
> the DOM window to return nsnull.  Instead they recommend replacing the
> code with npruntime API calls.  A discussion board post to
> mozilla.dev.tech.plugins yields more information[1].
> 
> Anyway, just thought I'd give you guys a heads up, and brighten your
> days a bit.  I know my day got brighter hearing that we'll have to ship
> two plugins for FF 3.5 and 3.6.  Yay!

Until the Moonlight team can refactor the Firefox plugin code, if you're
using Firefox from the mozilla-192 branch (aka Firefox 3.6), update to
r29558.  This is the last revision that contains XPCOM support.

Hope this helps,

-Brad



More information about the Moonlight-list mailing list