Assertion failure: hookPrincipals == compPrincipals ... at jsobjinlines.h:877




8 years ago
8 years ago


(Reporter: igor, Assigned: mrbkap)



Other Branch
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)


(Whiteboard: fixed-in-tracemonkey, )


(2 attachments)



8 years ago
I got the following assert when reading an articles on I could not reproduce it at will, but i managed to get it 3 times.

Assertion failure: hookPrincipals == compPrincipals || (hookPrincipals->subsume(hookPrincipals, compPrincipals) && compPrincipals->subsume(compPrincipals, hookPrincipals)), at /scratch/igor/m/tm/j/src/jsobjinlines.h:877

Comment 1

8 years ago
Posted file stack trace

Comment 2

8 years ago
This happens when I browsed using a VNC session on a server. I guess I can keep the debugger running for some time there.

Comment 3

8 years ago
To Luke: can it be a fallout from bug 602994?
Well, that assert was definitely added by bug 602994.  But its a property that should generally be true: the compartment containing an object should have equivalent principals to those found through findObjectPrincipals.  What are the two principals involved?

Comment 5

8 years ago

Well good to see this isn't some terrible chrome privilege leaking.  Igor: Blake was suspecting document.domain at play; do you see any evidence of this?

Comment 7

8 years ago
(In reply to comment #6)
> Igor:
> Blake was suspecting document.domain at play; do you see any evidence of this?

document.domain is set to on but not on articles like


8 years ago
Blocks: 651546

Comment 8

8 years ago
I got the same assert when browsing at (a Russian news site). It contains document.domain = ''.


8 years ago
Blocks: 602994
No longer blocks: 651546
Oh right, I talked to mrbkap about this IRL but then we got interrupted and the consensus was never recorded.

Blake explained that this is a problem where, even if two documents have the same domain, if only one of them sets document.domain, they get different (non-equivalent) principals.  Due to the lack of compartments==globals (bug 650353), this can lead to objects in the same compartment but with non-equivalent principals.  Blake explains this isn't a security hole because they must have started with the same principals, at which point, any evil actions could have happened.  Thus, the resolution was to delete the assert since there isn't anything weaker we could assert.  Furthermore, after bug 650353, the assert also wouldn't have much meaning since, IIUC, it would essentially be true by definition.
Posted patch Proposed fixSplinter Review
Assignee: general → mrbkap
Attachment #528974 - Flags: review?(luke)
But I thought you convinced me that the compartment's principals were good enough?  Or have you convinced yourself otherwise now?
Comment on attachment 528974 [details] [diff] [review]
Proposed fix

IRL answer from mrbkap: 'yes'
Attachment #528974 - Flags: review?(luke) → review+
So I see this assertion reliably while restoring a session.  In particular, I'm asserting on a script in:
while loading:
in a tab.

When I apply the fix (attachment 528974 [details] [diff] [review]), however, I still hit a fatal assertion... just a different one:

Assertion failure: callerPrincipals->subsume(callerPrincipals, calleePrincipals), at /home/dbaron/builds/ssd/mozilla-central/mozilla/js/src/jsobj.cpp:1344

In this case, in js::PrincipalsForCompiledCode, calleePrincipals->codebase
is ""
but unfortunately callerPrincipals is <value optimized out>.

Is that a continuation of this bug, or another one?

Comment 14

8 years ago
I've seen Assertion failure: hookPrincipals == compPrincipals  on a number of urls on Windows, Mac and 32bit as well as 64 bit Linux. It is quite common and will negatively impact crash testing the trunk. It would be very very nice if this landed soon.

We should open a second bug for the other compartment mismatch.
Whiteboard: fixed-in-tracemonkey
Last Resolved: 8 years ago
Resolution: --- → FIXED
It looks like the follow-up was just filed with bug 656171.
You need to log in before you can comment on or make changes to this bug.