Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[WebAssembly] ASSERTION 2257: ChakraCore v1.11.7
See original GitHub issueHello
I have validated that the test case for https://github.com/Microsoft/ChakraCore/issues/5985 runs correctly with a Debug version of ChakraCore and the small test case but there still seems to be something wrong when running against our tests and still receiving the following:
ASSERTION 2257: (/Users/Jimmy/websharp/projects/ChakraCore/lib/Backend/IRBuilderAsmJs.cpp, line 1044) !IsLoopBody() || offset <= GetLoopBodyExitInstrOffset()
Failure: (!IsLoopBody() || offset <= GetLoopBodyExitInstrOffset())
Illegal instruction: 4
Not sure how to create a small repo of this either. Is there some way to help narrow this down even further?
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (3 by maintainers)
Top Results From Across the Web
[WebAssembly] ASSERTION 2257: ChakraCore v1.11.7 · Issue ...
Hello I have validated that the test case for #5985 runs correctly with a Debug version of ChakraCore and the small test case...
Read more >Untitled
CISEC:5855, Chakra Scripting Engine Memory Corruption Vulnerability This affects Microsoft Edge, ChakraCore This CVE ID is unique from CVE-2018-8542, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m not a ChakraCore developer, but tried to download the test case and could not access it.
Yeah, unfortunately fix went in a little too late to make 1.11.8.