630875 - "Assertion failure: compartment mismatched,"

Status: RESOLVED DUPLICATE of bug 631409

(Core :: XPConnect, defect)

Description

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Attachment: stack and script->filename / script->lineno information

Compile a TM browser build, then install Adblock Plus 1.3.3, then head to about:addons to trigger this assert.

Tested on Ubuntu Linux 10.04 TM changeset 641a33d0932f.

.mozconfig is:

. $topsrcdir/browser/config/mozconfig
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/obj-ff-dbg-64-tm
mk_add_options MOZ_MAKE_FLAGS="-s -j4"
ac_add_options --enable-debug
ac_add_options --disable-optimize
ac_add_options --enable-tests

Comment 1

[Gary Kwong [:gkw] [:nth10sd] (NOT official MoCo now)]

Thanks go out to jorendorff for helping me out on IRC :)

Comment 2

[Andreas Gal :gal]

Reproduced.

Comment 3

[Andreas Gal :gal]

I updated to a fresh TM pull and the bug is gone, so this is WFM with TM tip. Please re-open if you still see this.

Comment 4

[Andreas Gal :gal]

Actually ran into this again with a slightly different stack :(

Comment 5

[Wladimir Palant]

Some context info: Adblock Plus (in particular, RequestNotifier.jsm mentioned here) attaches its data (object created by chrome) to content nodes using node.setUserData(). From the line number in the stack trace it is unclear which call is triggering the assertion, setUserData() or getUserData(), the line number is exactly in between. I would assume setUserData() however, the data usually isn't being retrieved without explicit user action (pressing Ctrl-Shift-V or checking the tooltip on the ABP icon).

Comment 6

[Johnny Stenback (:jst)]

My guess is that this is related to bug 631135, etc.

Comment 7

[Luke Wagner [:luke]]

If the native called by CallJSNative is XPC_WN_CallMethod or kin, could also be fixed by bug 627954.