Closed
Bug 717716
Opened 14 years ago
Closed 14 years ago
"Assertion failure: [infer failure] Missing type pushed 1: void,"
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 717252
| Tracking | Status | |
|---|---|---|
| firefox9 | --- | unaffected |
| firefox10 | --- | unaffected |
| firefox11 | --- | unaffected |
| firefox12 | + | fixed |
| status1.9.2 | --- | unaffected |
People
(Reporter: gkw, Unassigned)
References
Details
(Keywords: assertion, regression, testcase, Whiteboard: [sg:critical] fixed in bug 717252)
Attachments
(1 file)
|
6.92 KB,
text/plain
|
Details |
evalcx("function::print()", newGlobal("new-compartment"))
asserts js debug shell on m-c changeset 7c7d2a8db7ff with -m, -a and -n at Assertion failure: [infer failure] Missing type pushed 1: void,
Assuming s-s and [sg:critical] because type failures are bad.
autoBisect shows this is probably related to the following changeset:
The first bad revision is:
changeset: 84036:7ab4f1ebc7cc
user: Brian Hackett
date: Mon Jan 09 06:29:50 2012 -0800
summary: Backout 54cd89b0f1fa (bug 712714 backout). Talos will probably report fake regressions for this patch, do not back out for this reason.
This assert message is slightly different from bug 715149 and bug 717252.
Comment 1•14 years ago
|
||
If evalcx() is inaccessible from content this might only be [sg:moderate]. Are there other content-accessible ways to trigger the same bug?
status1.9.2:
--- → unaffected
status-firefox10:
--- → unaffected
status-firefox11:
--- → unaffected
status-firefox12:
--- → affected
status-firefox9:
--- → unaffected
tracking-firefox12:
--- → +
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Updated•14 years ago
|
Depends on: 717252
Whiteboard: [sg:critical] js-triage-needed → [sg:critical] fixed in bug 717252
Updated•14 years ago
|
Group: core-security
You need to log in
before you can comment on or make changes to this bug.
Description
•