Closed
Bug 1064159
Opened 10 years ago
Closed 10 years ago
Shumway hits SpiderMonkey assertion failure: !unknownProperties(), at js/src/jsinferinlines.h:1234
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla35
Tracking | Status | |
---|---|---|
firefox34 | --- | unaffected |
firefox35 | --- | affected |
People
(Reporter: cpeterson, Assigned: bhackett1024)
References
Details
(Keywords: assertion, regression, reproducible)
Attachments
(2 files)
1.05 KB,
patch
|
jandem
:
review+
|
Details | Diff | Splinter Review |
95.68 KB,
text/plain
|
Details |
Comment hidden (obsolete) |
Reporter | ||
Comment 1•10 years ago
|
||
Brian: this assertion failure is a regression from your "Singleton type set fix" bug 1041688 comment 40:
https://hg.mozilla.org/integration/mozilla-inbound/rev/7b20a4e9ce15
I saw hits assertion failure after the new (TypeScript) version of Shumway was merged to mozilla-central on 2014-08-05 (bug 1061888).
STR:
1. Enable Shumway by flipping about:config pref "shumway.disabled" to false.
2. Running a debug build, load Flash site http://www.zombo.com
RESULT:
Assertion failure: !unknownProperties(), at js/src/jsinferinlines.h:1234
Reporter | ||
Updated•10 years ago
|
status-firefox34:
--- → unaffected
Summary: Shumway hits assertion failure: !unknownProperties(), at js/src/jsinferinlines.h:1234 → Shumway hits SpiderMonkey assertion failure: !unknownProperties(), at js/src/jsinferinlines.h:1234
Assignee | ||
Comment 2•10 years ago
|
||
The APIs for updating type properties are pretty convoluted and after this lands I'll write a patch to clean them up.
Assignee: nobody → bhackett1024
Attachment #8487943 -
Flags: review?(jdemooij)
Flags: needinfo?(bhackett1024)
Updated•10 years ago
|
Attachment #8487943 -
Flags: review?(jdemooij) → review+
Assignee | ||
Comment 3•10 years ago
|
||
I just hit this loading https://www.flickr.com/photos/dbaron/
Comment 5•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
You need to log in
before you can comment on or make changes to this bug.