All users were logged out of Bugzilla on October 13th, 2018

"Assertion failure: compartment mismatched" with chrome-content interaction

RESOLVED WORKSFORME

Status

()

--
critical
RESOLVED WORKSFORME
8 years ago
8 years ago

People

(Reporter: jruderman, Unassigned)

Tracking

(Blocks: 1 bug, {assertion, testcase})

Trunk
x86_64
Windows 7
assertion, testcase
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

8 years ago
Created attachment 482423 [details]
testcase (requires extension)

[Tested a browser build from TM branch, post-Compartments landing]

1. Temporarily install 'DOM Fuzz Lite' from
    https://www.squarefree.com/extensions/domFuzzLite.xpi
2. Load the testcase.

Result:

Assertion failure: compartment mismatched, at js/src/jscntxtinlines.h:513
(Reporter)

Comment 1

8 years ago
The relevant part of the extension is injecting this function into every content global object:

function runSoon(f)
{
  var tm = Components.classes["@mozilla.org/thread-manager;1"]
             .getService(Components.interfaces.nsIThreadManager);

  tm.mainThread.dispatch({
    run: function() {
      f();
    }
  }, Components.interfaces.nsIThread.DISPATCH_NORMAL);
}
(Reporter)

Comment 2

8 years ago
Blake says the patch in bug 610941 should fix this.
Depends on: 610941
OS: Mac OS X → Windows 7

Updated

8 years ago
Depends on: 618871
(Reporter)

Comment 3

8 years ago
WFM on trunk.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.