issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"chakra-core",
"ChakraCore"
] | ###### ChakraCore version:
version 1.12.0.0-beta
###### Build Commond
./build.sh --debug
###### OS
Ubuntu 16.04.6 LTS (Linux 4.4.0-142-generic x86_64)
###### Test case
```
function test0() {
var func2 = (async (xsbazt = hkvvxr(x)) => [...[
-2,
]]);
var a = -191;
func3(a);
}
fu... | ASSERTION (pFuncBody->GetYieldRegister() == oldYieldRegister) failed in Js::DebugContext::RundownSourcesAndReparse | https://api.github.com/repos/chakra-core/ChakraCore/issues/6453/comments | 0 | 2020-06-01T09:03:35Z | 2020-06-09T03:10:58Z | https://github.com/chakra-core/ChakraCore/issues/6453 | 628,271,379 | 6,453 |
[
"chakra-core",
"ChakraCore"
] | Hi. Is there a way to break an endless loop?
In example, I have some script that contains endless loop, and I can't check it before execution.
I want to destroy a runtime instance after delay, but I'm getting exception with message "A runtime that is still in use cannot be disposed". | Break endless loop | https://api.github.com/repos/chakra-core/ChakraCore/issues/6452/comments | 2 | 2020-06-01T07:29:43Z | 2020-06-01T08:53:23Z | https://github.com/chakra-core/ChakraCore/issues/6452 | 628,217,902 | 6,452 |
[
"chakra-core",
"ChakraCore"
] | Tracking: WebAssembly [reference types][r] proposal is attempting to go to Phase 4. Obviously it is not going to be trivial amount of work to implement. Upside of trying to this proposal is that it is in a mature stage and won't change much. It might also be useful for embedded scenarios.
[r]: https://github.com/Web... | [Wasm] Reference types | https://api.github.com/repos/chakra-core/ChakraCore/issues/6451/comments | 0 | 2020-05-27T02:08:33Z | 2020-05-27T02:08:33Z | https://github.com/chakra-core/ChakraCore/issues/6451 | 625,319,849 | 6,451 |
[
"chakra-core",
"ChakraCore"
] | Hello! Here is an example integration with full debugger capabilities I wanted to share.
It also shows how to project objects to Javascript easily via reflection.
Is a great API you come with! Thank you.
https://bitbucket.org/Adr14n/chakracore-.net-integration-example/src/master/ | Example of .Net Integration | https://api.github.com/repos/chakra-core/ChakraCore/issues/6450/comments | 1 | 2020-05-26T13:23:08Z | 2020-05-29T10:20:21Z | https://github.com/chakra-core/ChakraCore/issues/6450 | 624,880,302 | 6,450 |
[
"chakra-core",
"ChakraCore"
] | As one can't give native funcions objects a name (name property of function objects is read only) looks like there is no way to make instanceof to work on external objects. Is there any workaround? | instanceof not working with external objects | https://api.github.com/repos/chakra-core/ChakraCore/issues/6448/comments | 8 | 2020-05-18T15:56:24Z | 2020-05-19T14:58:50Z | https://github.com/chakra-core/ChakraCore/issues/6448 | 620,323,913 | 6,448 |
[
"chakra-core",
"ChakraCore"
] | There are various issues with the test suite that make it harder to maintain and use than it should be. Each of these should be addressed. However this obviously won't improve the experience for any users of ChakraCore it's a purely for developer/contributor experience hence this is low priority but still something to ... | Test Suite Cleanup | https://api.github.com/repos/chakra-core/ChakraCore/issues/6445/comments | 1 | 2020-05-09T10:49:20Z | 2021-02-25T08:50:03Z | https://github.com/chakra-core/ChakraCore/issues/6445 | 615,148,180 | 6,445 |
[
"chakra-core",
"ChakraCore"
] | There are a few CMake build options for ICU currently:
- `NO_ICU` disables building with ICU support
- `SYSTEM_ICU` triggers default ICU link libraries to be used
- `EMBED_ICU` download ICU sources, then build and use them during build
- `ICU_INCLUDE_PATH` custom ICU installation (just the include path)
There ... | CMake ICU options | https://api.github.com/repos/chakra-core/ChakraCore/issues/6443/comments | 0 | 2020-05-08T14:38:25Z | 2020-05-08T14:38:25Z | https://github.com/chakra-core/ChakraCore/issues/6443 | 614,783,746 | 6,443 |
[
"chakra-core",
"ChakraCore"
] | Hello,
I am able to reproduce the following bug still with NuGet package 1.11.17 using the code above
`eval("a/("+Array(2**16).fill(0).join(",")+")");`
This was closed out a while back https://github.com/Microsoft/ChakraCore/issues/5699 so I thought I would create a new issue. | Crash regression for eval("a/("+Array(2**16).fill(0).join(",")+")"); | https://api.github.com/repos/chakra-core/ChakraCore/issues/6438/comments | 1 | 2020-04-27T16:51:51Z | 2020-04-27T19:20:23Z | https://github.com/chakra-core/ChakraCore/issues/6438 | 607,699,375 | 6,438 |
[
"chakra-core",
"ChakraCore"
] | Chakra failed when build with std:c++latest by msvc on Windows. Could you please help take a look at this?
**You can repro this issue as the steps below:**
1. git clone -c core.autocrlf=true https://github.com/microsoft/ChakraCore D:\Chakra\src
2. open a clean VS2019 x86 prompt and browse to D:\Chakra\src
3. se... | Chakra failed when build with std:c++latest by msvc on Windows | https://api.github.com/repos/chakra-core/ChakraCore/issues/6436/comments | 7 | 2020-04-23T09:52:56Z | 2020-05-15T11:37:47Z | https://github.com/chakra-core/ChakraCore/issues/6436 | 605,397,249 | 6,436 |
[
"chakra-core",
"ChakraCore"
] | While working on #6430 I've noticed that there are no includes for `unicode/uchar.h`, which was puzzling at first, but then I realized that`-Wno-implicit-function-declaration` set up in CMake inhibits complaints about that.
Implicit function declarations are dangerous, because they can hide mismatches between defini... | Warning switches | https://api.github.com/repos/chakra-core/ChakraCore/issues/6435/comments | 1 | 2020-04-22T03:30:16Z | 2020-05-15T16:51:02Z | https://github.com/chakra-core/ChakraCore/issues/6435 | 604,426,252 | 6,435 |
[
"chakra-core",
"ChakraCore"
] | Need to catch up with the state of `simd128` WebAssembly proposal, though it might make sense to wait until after the opcode renumbering - WebAssembly/simd#209.
There is a number of new operations, in particular `swizzle` had been reintroduced, but with variable mask; general case would be expensive to implement wit... | simd128 opcode update and new instructions | https://api.github.com/repos/chakra-core/ChakraCore/issues/6434/comments | 1 | 2020-04-22T03:07:35Z | 2020-04-22T03:10:33Z | https://github.com/chakra-core/ChakraCore/issues/6434 | 604,418,567 | 6,434 |
[
"chakra-core",
"ChakraCore"
] | There is some ICU detection as part of PAL (it checks for `uchar.h`), but ChakraCore main CMake file does not really look for the library, unless `ICU_INCLUDE_PATH` is set.
For 'system ICU` case Linux distros get hardcoded library names, and OSX does not get anything set.
We might need to think what the interacti... | Detect ICU from CMake | https://api.github.com/repos/chakra-core/ChakraCore/issues/6433/comments | 0 | 2020-04-22T00:51:03Z | 2020-04-22T00:53:07Z | https://github.com/chakra-core/ChakraCore/issues/6433 | 604,374,128 | 6,433 |
[
"chakra-core",
"ChakraCore"
] | There are currently a few problems with using test262 efficiently on chakracore:
1. ch does not support monotonicNow (see issue #5271)
2. I'm unsure if the createRealm method works properly - some tests relating to it fail - though it could be that that's exposing underlying CC issues.
3. Some spec violations may ... | Efficient use of test262 | https://api.github.com/repos/chakra-core/ChakraCore/issues/6432/comments | 1 | 2020-04-21T08:34:00Z | 2020-12-14T18:38:56Z | https://github.com/chakra-core/ChakraCore/issues/6432 | 603,813,620 | 6,432 |
[
"chakra-core",
"ChakraCore"
] | Contents of `test/benchmarks`
```
ARES-6
jetstream
Kraken
Octane
Octane_Closure
SunSpider
```
Should we add or update anything? One thing I can think from the top of my head, is that Jetstream has a new version (which also includes Wasm).
@chicoxyzzy and @zenparsing what do you think about this from set... | Benchmarks | https://api.github.com/repos/chakra-core/ChakraCore/issues/6431/comments | 1 | 2020-04-21T02:55:30Z | 2020-05-15T16:19:43Z | https://github.com/chakra-core/ChakraCore/issues/6431 | 603,666,940 | 6,431 |
[
"chakra-core",
"ChakraCore"
] | The version returned by https://aka.ms/chakracore/version is `1_11_18`, but requesting the build itself (https://aka.ms/chakracore/cc_osx_x64_1_11_18) returns a 403 error | https://aka.ms/chakracore/cc_osx_x64_1_11_18 returning "AuthenticationFailed" | https://api.github.com/repos/chakra-core/ChakraCore/issues/6428/comments | 2 | 2020-04-20T14:42:30Z | 2020-04-21T01:49:16Z | https://github.com/chakra-core/ChakraCore/issues/6428 | 603,292,287 | 6,428 |
[
"chakra-core",
"ChakraCore"
] | https://aka.ms/chakracore/cc_osx_x64_1_11_18 | ChakraCore builds returning 403 errors for "1_11_18 | https://api.github.com/repos/chakra-core/ChakraCore/issues/6427/comments | 2 | 2020-04-20T14:39:30Z | 2020-04-21T01:50:38Z | https://github.com/chakra-core/ChakraCore/issues/6427 | 603,290,134 | 6,427 |
[
"chakra-core",
"ChakraCore"
] | Current *nix builds allow for embedding of ICU library into the build via `--embed-icu` switch. What this does - it invokes an additional script from the build script, followed by `configure` and `make`:
https://github.com/microsoft/ChakraCore/blob/master/build.sh#L411
https://github.com/microsoft/ChakraCore/blob/m... | Embed ICU from CMake | https://api.github.com/repos/chakra-core/ChakraCore/issues/6424/comments | 6 | 2020-04-17T01:42:40Z | 2020-05-07T05:36:08Z | https://github.com/chakra-core/ChakraCore/issues/6424 | 601,642,563 | 6,424 |
[
"chakra-core",
"ChakraCore"
] | I've noticed that `runtests.py` does not support testing release binary. If I try to force it run (with "test" or "debug" flag), all the tests seem to fail.
Does anybody remember why? | Running tests on release build | https://api.github.com/repos/chakra-core/ChakraCore/issues/6422/comments | 11 | 2020-04-15T02:40:43Z | 2020-05-17T05:23:05Z | https://github.com/chakra-core/ChakraCore/issues/6422 | 599,977,481 | 6,422 |
[
"chakra-core",
"ChakraCore"
] | Build type `Test` in CMakeLists.txt corresponds to default CMake build type `RelWithDebInfo` (release with debug on).
There is also a section that sets up `-O0` for `Debug`, `-O3` for release and so on, which should not be necessary.
`Test` build type is tied to `--test` flag in the script, but `RelWithDebInfo` c... | RelWithDebInfo build type | https://api.github.com/repos/chakra-core/ChakraCore/issues/6419/comments | 0 | 2020-04-14T07:41:28Z | 2020-04-22T02:17:14Z | https://github.com/chakra-core/ChakraCore/issues/6419 | 599,363,568 | 6,419 |
[
"chakra-core",
"ChakraCore"
] | On platforms on which ChacoreCore builds via CMake allow the canonical CMake workflow. In the most basic case it would be something like this (`ninja` generator should be enabled as well):
```
$ cd build
$ cmake /path/to/ChakraCore/
$ make
```
- [x] (Basic workflow)
Extra credit:
- [x] testing support
- ... | Default CMake builds | https://api.github.com/repos/chakra-core/ChakraCore/issues/6417/comments | 0 | 2020-04-14T02:53:47Z | 2020-05-13T16:49:09Z | https://github.com/chakra-core/ChakraCore/issues/6417 | 599,259,150 | 6,417 |
[
"chakra-core",
"ChakraCore"
] | The CC external API also called JSRT could do with a review prior to the next release.
Roughly speaking it contains:
1. "Windows only APIs":
These are historic chakra.dll APIs that pre-date the cross platform nature of chakracore; they can actually be used on linux or macOS with some caution - notably they use str... | Review Hosting API | https://api.github.com/repos/chakra-core/ChakraCore/issues/6416/comments | 8 | 2020-04-13T09:16:03Z | 2020-05-11T09:27:53Z | https://github.com/chakra-core/ChakraCore/issues/6416 | 598,776,785 | 6,416 |
[
"chakra-core",
"ChakraCore"
] | ChakraCore contains numerous feature switches that in practise are never used - e.g. there's a switch to disable promises and one to disable proxies etc. Some of these bloat the codebase AND require runtime checks for whether they're enabled or not.
EDIT: we should also consider removing phase/option switches that a... | Review feature switches/Remove old always on switches | https://api.github.com/repos/chakra-core/ChakraCore/issues/6415/comments | 1 | 2020-04-11T19:25:26Z | 2020-12-05T17:10:43Z | https://github.com/chakra-core/ChakraCore/issues/6415 | 598,334,374 | 6,415 |
[
"chakra-core",
"ChakraCore"
] | As part of improving the experience for contributors we should produce helpful documentation covering the logic of ChakraCore's internals. Including what the key data types are in each area and what key logical processes are used internally:
It would be good if multiple people could contribute to this, we'll need to... | Documenting ChakraCore's internals | https://api.github.com/repos/chakra-core/ChakraCore/issues/6414/comments | 1 | 2020-04-11T19:14:36Z | 2020-04-25T18:26:43Z | https://github.com/chakra-core/ChakraCore/issues/6414 | 598,332,405 | 6,414 |
[
"chakra-core",
"ChakraCore"
] | Looks like there are a few scripting languages used for various tasks:
```
$ find ChakraCore -name \*.bat -o -name \*.cmd -o -name \*.ps1 -o -name \*.py -o -name \*.pl -o -name \*.sh | grep -o "\(cmd\|ps1\|py\|pl\|sh\|bat\)" | sort | uniq -c
1 bat
26 cmd
3 pl
14 ps1
13 py
15 sh
```
One issue... | Scripts (and scripting languages) | https://api.github.com/repos/chakra-core/ChakraCore/issues/6411/comments | 13 | 2020-04-11T02:57:44Z | 2021-01-28T05:08:48Z | https://github.com/chakra-core/ChakraCore/issues/6411 | 598,175,183 | 6,411 |
[
"chakra-core",
"ChakraCore"
] | The JsBuiltIn system makes cross-platform development difficult, since:
- The scripts to regenerate the bytecode are written for the windows command shell.
- x86 isn't even supported on Mac, etc.
Also, dealing with bytecode regeneration is a constant source of conflicts and annoyance.
So a couple of questions... | Questions about JsBulitIn | https://api.github.com/repos/chakra-core/ChakraCore/issues/6410/comments | 26 | 2020-04-11T02:46:56Z | 2020-04-20T17:54:15Z | https://github.com/chakra-core/ChakraCore/issues/6410 | 598,173,589 | 6,410 |
[
"chakra-core",
"ChakraCore"
] | I [already wrote](https://github.com/microsoft/ChakraCore/pull/6403#issuecomment-608331434) that when switching from version 1.11.17 to version 1.12.0, in my project some tests stopped passing:
```
Expected: ···riable2 - variable3;
Actual: ···riable2 - variable3;\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0... | Different length of the error source in 1.11 and 1.12 versions | https://api.github.com/repos/chakra-core/ChakraCore/issues/6408/comments | 4 | 2020-04-10T14:21:17Z | 2020-04-11T16:49:31Z | https://github.com/chakra-core/ChakraCore/issues/6408 | 597,913,724 | 6,408 |
[
"chakra-core",
"ChakraCore"
] | This is an idea I thought of whilst looking at #6341
Throughout the internal JS library in ChakraCore a method `GetAndAssertIsConstructorSuperCall` is used within all constructors to see if they are being called as supers or potentially have a newTarget set. All of these checks:
a) have a small but pervasive perfor... | Suggestion: extract IsConstructorSuperCall into callers and use templates | https://api.github.com/repos/chakra-core/ChakraCore/issues/6407/comments | 0 | 2020-04-09T09:52:25Z | 2020-04-09T10:21:01Z | https://github.com/chakra-core/ChakraCore/issues/6407 | 597,162,858 | 6,407 |
[
"chakra-core",
"ChakraCore"
] | This is mostly to get some clarity on when/if we should move community driven development to a different Github organization, as outlined in #6399.
We have created https://github.com/chakra-core with the members of the community team invited.
Creating a separate repo should involve moving or copying the issues fr... | Decide on the home for the repo | https://api.github.com/repos/chakra-core/ChakraCore/issues/6406/comments | 6 | 2020-04-07T06:13:18Z | 2020-04-14T02:39:48Z | https://github.com/chakra-core/ChakraCore/issues/6406 | 595,618,295 | 6,406 |
[
"chakra-core",
"ChakraCore"
] | **EDIT:** ideal goal is to remove all dependence on PAL, but this will be a large project
1. PAL was added to ChakraCore in ~2016 to make it build on Linux and MacOS.
2. Since then it has been updated a little - occasionally new content from dotnet has been brought over but not in a full or systematic way.
3. ... | PAL compatibility issues | https://api.github.com/repos/chakra-core/ChakraCore/issues/6404/comments | 10 | 2020-04-03T08:01:50Z | 2024-04-25T05:05:21Z | https://github.com/chakra-core/ChakraCore/issues/6404 | 593,195,612 | 6,404 |
[
"chakra-core",
"ChakraCore"
] | Review how error locations are displayed.
Spec discussion: https://github.com/WebAssembly/design/pull/1053 | Standard wasm Error location | https://api.github.com/repos/chakra-core/ChakraCore/issues/6402/comments | 0 | 2020-04-02T02:56:28Z | 2020-04-02T02:56:28Z | https://github.com/chakra-core/ChakraCore/issues/6402 | 592,322,702 | 6,402 |
[
"chakra-core",
"ChakraCore"
] | Should we add Gitter or Discord (or both)?
I recall @Fly-Style has some experience with it. | Instant communication | https://api.github.com/repos/chakra-core/ChakraCore/issues/6401/comments | 6 | 2020-04-01T07:30:04Z | 2020-04-11T13:32:06Z | https://github.com/chakra-core/ChakraCore/issues/6401 | 591,690,597 | 6,401 |
[
"chakra-core",
"ChakraCore"
] | I'm trying to understand the capability of ChakraCore in regards to multi-threaded environment with multiple run times and multiple contexts.
We are currently using an older version of Spidermonkey which gives us full control of global objects and can have multiple threads access objects at the same time.
I know ... | Question - globals, contexts & threading | https://api.github.com/repos/chakra-core/ChakraCore/issues/6400/comments | 5 | 2020-03-31T23:49:01Z | 2020-04-02T18:34:31Z | https://github.com/chakra-core/ChakraCore/issues/6400 | 591,515,141 | 6,400 |
[
"chakra-core",
"ChakraCore"
] | ###### Test Case
```
print(/\udc00/u.test('\udc00\uDC2A'));
print(/\ud800/u.test('\ud800\uDC2A'));
```
###### Excepted Output
true
false
###### Chakra Output
true
true
###### Other JS Engines Output
true
false
###### Description
Is this a bug in chakra? Or is it just that chakr is coded different... | A issue about Regex with flag 'u'. | https://api.github.com/repos/chakra-core/ChakraCore/issues/6398/comments | 2 | 2020-03-31T04:44:54Z | 2020-03-31T10:50:53Z | https://github.com/chakra-core/ChakraCore/issues/6398 | 590,788,685 | 6,398 |
[
"chakra-core",
"ChakraCore"
] | @Cellule - I've added #6396 and put it up as "bug" [WebAssemply project](https://github.com/microsoft/ChakraCore/projects/1), though it does not necessary a bug (at least from correctness point of view). I am not sure what to do with priority here - what were your thoughts on P1, P2, P3 buckets? | Rearranging WebAssembly project | https://api.github.com/repos/chakra-core/ChakraCore/issues/6397/comments | 2 | 2020-03-31T03:45:13Z | 2020-04-01T07:33:10Z | https://github.com/chakra-core/ChakraCore/issues/6397 | 590,766,684 | 6,397 |
[
"chakra-core",
"ChakraCore"
] | Current implementation of wasm SIMD shuffle produces a scalar loop over the bytes of the vector. That is the leftover of the situation when there were multiple shuffles with different lane shuffles - byte shuffle was considered lower priority than other kinds.
To solve this Chakra would need to emit byteshuffle inst... | WASM SIMD - Single instruction shuffle | https://api.github.com/repos/chakra-core/ChakraCore/issues/6396/comments | 2 | 2020-03-31T03:12:19Z | 2021-10-30T07:58:42Z | https://github.com/chakra-core/ChakraCore/issues/6396 | 590,753,446 | 6,396 |
[
"chakra-core",
"ChakraCore"
] | As discussed in #6384, there is value in improving CMake experience for non-MSVC developers.
I think we should provide first-class CMake build flow, in addition to the script. This should improve development experience - by using usual CMake patterns, and consolidating everything build-related "under one roof", by i... | CMake improvements | https://api.github.com/repos/chakra-core/ChakraCore/issues/6392/comments | 4 | 2020-03-30T08:40:21Z | 2020-04-14T02:59:27Z | https://github.com/chakra-core/ChakraCore/issues/6392 | 590,100,854 | 6,392 |
[
"chakra-core",
"ChakraCore"
] | ES6 regular expression prototype and symbol features were never fully implemented or enabled - this is the one signficant ES6 gap that Chakracore still has.
The two flags: -ES6RegexPrototypeProperties and -ES6RegexSymbols guard much of this incomplete work.
These need a thorough review/clean up and then to be ena... | RegExp ES6 implementation incomplete | https://api.github.com/repos/chakra-core/ChakraCore/issues/6390/comments | 0 | 2020-03-25T08:52:25Z | 2021-02-13T15:11:49Z | https://github.com/chakra-core/ChakraCore/issues/6390 | 587,539,154 | 6,390 |
[
"chakra-core",
"ChakraCore"
] | Hello everyone,
In December of 2018, [we announced](https://blogs.windows.com/windowsexperience/2018/12/06/microsoft-edge-making-the-web-better-through-more-open-source-collaboration/) our intent to adopt the Chromium Open Source project in the development of Microsoft Edge. At that time, [we made no immediate chang... | ChakraCore Transition | https://api.github.com/repos/chakra-core/ChakraCore/issues/6384/comments | 30 | 2020-03-09T18:08:53Z | 2020-05-05T20:13:58Z | https://github.com/chakra-core/ChakraCore/issues/6384 | 578,094,462 | 6,384 |
[
"chakra-core",
"ChakraCore"
] | When I execute the testcase below, chakra gives a different output which is not the same as other engines (like V8, spiderMonkey,javascriptCore). I wonder if chakra has any special ways to deal with floating numbers.
### version
[eaaf7ac](https://github.com/microsoft/ChakraCore/commit/eaaf7ac6beca01ab0d80c05959f38684... | A question about floating number | https://api.github.com/repos/chakra-core/ChakraCore/issues/6383/comments | 4 | 2020-03-09T13:55:50Z | 2020-06-12T11:55:53Z | https://github.com/chakra-core/ChakraCore/issues/6383 | 577,927,352 | 6,383 |
[
"chakra-core",
"ChakraCore"
] | In the downloaded nuget package
packages\Microsoft.ChakraCore.vc140.1.11.10\lib\native\v140
It has arm, x64, and x86 but no arm64
Should the nuget have it?
Note:
Also just checked latest
Microsoft.ChakraCore.vc140.1.11.16
still not there :( | The nuget for ChakraCore.vc140 by Microsoft doesn't include arm64 | https://api.github.com/repos/chakra-core/ChakraCore/issues/6382/comments | 2 | 2020-03-03T23:32:01Z | 2020-08-21T02:35:47Z | https://github.com/chakra-core/ChakraCore/issues/6382 | 575,027,414 | 6,382 |
[
"chakra-core",
"ChakraCore"
] | **Description:**
In /std:c++17 mode, this triggers a deprecation warning in recent versions of MSVC. In /std:c++latest mode, now that microsoft/STL#380 has been merged, this will trigger an error in VS 2019 16.6 Preview 2.
**Reproduce steps:**
1. git clone -c core.autocrlf=true https://github.com/microsoft/ChakraC... | C++20 removed std::uncaught_exception | https://api.github.com/repos/chakra-core/ChakraCore/issues/6378/comments | 1 | 2020-02-17T07:16:34Z | 2020-05-15T11:35:28Z | https://github.com/chakra-core/ChakraCore/issues/6378 | 566,101,031 | 6,378 |
[
"chakra-core",
"ChakraCore"
] | #### Description
When running the testcase below, a SyntaxError exception should be thrown while chakra does not.
According to ES10, the `Expression` in parentheses of `IfStatement` should executed based on [this step](http://www.ecma-international.org/ecma-262/10.0/index.html#sec-comma-operator-runtime-semantics-ev... | An issue of the If Statement | https://api.github.com/repos/chakra-core/ChakraCore/issues/6377/comments | 13 | 2020-02-14T13:19:10Z | 2021-01-16T00:30:31Z | https://github.com/chakra-core/ChakraCore/issues/6377 | 565,322,273 | 6,377 |
[
"chakra-core",
"ChakraCore"
] | The C++20 draft standard incorporates a change to help avoid confusion when inserting inappropriate character types to iostreams. In previous C++ versions, insertion of inappropriate character types into output streams (e.g., `wchar_t`/`char16_t`/`char32_t` into `std::cout`) doesn't result in transcoding of the charact... | C++20 will break the build | https://api.github.com/repos/chakra-core/ChakraCore/issues/6374/comments | 1 | 2020-02-08T01:55:44Z | 2020-02-08T02:38:39Z | https://github.com/chakra-core/ChakraCore/issues/6374 | 561,952,853 | 6,374 |
[
"chakra-core",
"ChakraCore"
] | See: https://github.com/tc39/ecma262/issues/1794
Refs: https://github.com/microsoft/ChakraCore/issues/588
```
$ eshost -ts -e "[EvalError.prototype.hasOwnProperty('toString') ? 'own' : 'inherited', EvalError.prototype.toString === Error.prototype.toString ? 'eq' : 'ne']"
┌────────────────┬──────────────┐
│ Cha... | %NativeError%.prototype.toString duplicates Error.prototype.toString | https://api.github.com/repos/chakra-core/ChakraCore/issues/6372/comments | 0 | 2020-01-21T17:09:25Z | 2020-04-12T00:34:16Z | https://github.com/chakra-core/ChakraCore/issues/6372 | 553,012,776 | 6,372 |
[
"chakra-core",
"ChakraCore"
] | Attempting to evaluate a variable which exists in module scope, for example an `import`ed identifier, while paused at a breakpoint inside a function within that same module, will throw a ReferenceError, as though the identifier isn’t in scope. | Can’t access module-level variables from debugger breakpoint | https://api.github.com/repos/chakra-core/ChakraCore/issues/6369/comments | 2 | 2020-01-10T16:57:35Z | 2020-03-25T10:34:51Z | https://github.com/chakra-core/ChakraCore/issues/6369 | 548,187,266 | 6,369 |
[
"chakra-core",
"ChakraCore"
] | The bug can be reproduced in ch version 1.11.15.0.
Running following code:
```
let temp = eval('42;switch (0) { case 0: break; };');
console.log(temp);
```
Actual results:
`42`
Expected results:
`undefined`
According to ecma manual,https://tc39.es/ecma262/#sec-block-runtime-semantics-evaluation, the v... | Wrong completion value when switch is part of a statement list | https://api.github.com/repos/chakra-core/ChakraCore/issues/6368/comments | 1 | 2019-12-26T06:15:19Z | 2020-03-25T10:41:30Z | https://github.com/chakra-core/ChakraCore/issues/6368 | 542,447,183 | 6,368 |
[
"chakra-core",
"ChakraCore"
] | The bug can reproduce in ch version 1.11.15.0.
Running following code:
```
var obj = new Object();
Promise.race(obj);
```
According to ECMA manual, since `obj` is not iterable object, a TypeError should be thrown. However, ch output nothing.
ISec Lab
2019.12.25 | Fail to throw TypeError in Promise.race | https://api.github.com/repos/chakra-core/ChakraCore/issues/6367/comments | 4 | 2019-12-25T08:50:52Z | 2020-03-25T08:34:07Z | https://github.com/chakra-core/ChakraCore/issues/6367 | 542,295,977 | 6,367 |
[
"chakra-core",
"ChakraCore"
] | The bug can be reproduced in ch version 1.11.15.0.
Executing following code:
```
var i = 0;
function func(obj0) {
{
obj0.c = obj0.a;
}
}
function f() {
try {
f();
} catch (e) {
i++;
func(Array(123456789)); // can not delete
}
}
f();
print(i);
```
... | Handle statements in CatchClause incorrectly when stack overflow | https://api.github.com/repos/chakra-core/ChakraCore/issues/6366/comments | 1 | 2019-12-25T08:11:34Z | 2020-11-03T13:31:50Z | https://github.com/chakra-core/ChakraCore/issues/6366 | 542,288,419 | 6,366 |
[
"chakra-core",
"ChakraCore"
] | The bug can be reproduced in ch version 1.11.15.0.
code:
```
class c extends(d = function() {
return 0;
}, d) {};
```
ChakraCore print nothing, however, it should throw an error.
According to ecma-262
• All parts of a ClassDeclaration or a ClassExpression are strict mode code.
• In strict mode code,... | Not using strict mode within ClassDeclaration statement | https://api.github.com/repos/chakra-core/ChakraCore/issues/6365/comments | 1 | 2019-12-24T09:12:53Z | 2020-03-25T16:57:06Z | https://github.com/chakra-core/ChakraCore/issues/6365 | 542,056,475 | 6,365 |
[
"chakra-core",
"ChakraCore"
] | The bug can reproduce in ch version 1.11.15.0.
Running following code:
```
let arg_0 = /^([^(]+?)=>/;
let handler_0 = {
get: function(oTarget, sKey) {
return Reflect.get(oTarget, sKey);
},
};
let p_0 = new Proxy(arg_0, handler_0);
sym = Symbol.prototype.constructor(p_0);
print("BT_FLAG");
le... | ChakraCore throw an TypeError Incorrectly | https://api.github.com/repos/chakra-core/ChakraCore/issues/6364/comments | 1 | 2019-12-24T05:19:10Z | 2020-03-25T10:36:50Z | https://github.com/chakra-core/ChakraCore/issues/6364 | 541,994,681 | 6,364 |
[
"chakra-core",
"ChakraCore"
] | I run the following code in Characore-1.11.15 and get a very odd output. I do not know why the output is so strange. The two print should be same output, both 0. However, the first is -5 in ch. I think there must be something wrong in ch's realization.
The code:
```
var tmp = new Date() - new((2, function() { return... | Wrong realization of 'minus operation' [maybe] of Date object | https://api.github.com/repos/chakra-core/ChakraCore/issues/6363/comments | 1 | 2019-12-22T05:44:59Z | 2020-03-30T13:40:07Z | https://github.com/chakra-core/ChakraCore/issues/6363 | 541,411,412 | 6,363 |
[
"chakra-core",
"ChakraCore"
] | I run the following code in Characore-1.11.15 and get an odd output. The code firstly call the function ‘foo’, at this time, it print “false”. But then, when calling the ‘foo’ again in the ‘sort’, it print “true”. So I think a bug maybe exists in the implementation of ‘Array.prototype.sort’. This bug may affect the sor... | A bug of ‘Array.prototype.sort' | https://api.github.com/repos/chakra-core/ChakraCore/issues/6362/comments | 1 | 2019-12-22T04:57:35Z | 2020-03-25T08:40:10Z | https://github.com/chakra-core/ChakraCore/issues/6362 | 541,407,864 | 6,362 |
[
"chakra-core",
"ChakraCore"
] | I run following code in ch 1.11.15, the result of ChakraCore is different from other js engines. Though in specification, “string-concatenation” is not defined clearly, other engines’ output is same.
Code:
```
let arg_0 = ['Fire', '', 'Wind', 'Rain'];
arr2 = arg_0.toLocaleString();
print(JSON.stringify(arr2))
... | Array.prototype.toLocaleString uses comma space separator instead of just comma | https://api.github.com/repos/chakra-core/ChakraCore/issues/6361/comments | 7 | 2019-12-22T04:57:11Z | 2020-10-27T02:22:04Z | https://github.com/chakra-core/ChakraCore/issues/6361 | 541,407,830 | 6,361 |
[
"chakra-core",
"ChakraCore"
] | ubuntu 18.04.3
chakra (fd545b4)
test.js
```javascript
let arr1 = [];
function f1() {
try {
f1();
} catch (v1) {
for (let i = 0; i < 0x15555; i = i + 5) {
arr1[i] = 13.37;
}
let typearr1 = new Uint8Array(arr1);
typearr1.sort();
}
}
f1();... | Segmentation fault `sort recursion` | https://api.github.com/repos/chakra-core/ChakraCore/issues/6356/comments | 1 | 2019-12-17T07:45:35Z | 2019-12-18T01:36:46Z | https://github.com/chakra-core/ChakraCore/issues/6356 | 538,894,959 | 6,356 |
[
"chakra-core",
"ChakraCore"
] | When objects are deleted?
I guessed it's similar to COM.
So I guessed every created object has 1 reference and It will not be deleted
And I released every created object at the end.
But It's crashed sometimes.
So I tried to check the reference count, and the created object had 0 references.
I'm confused.
I... | Question about reference count, when it's deleted? | https://api.github.com/repos/chakra-core/ChakraCore/issues/6354/comments | 4 | 2019-12-13T08:21:46Z | 2019-12-13T16:24:18Z | https://github.com/chakra-core/ChakraCore/issues/6354 | 537,410,640 | 6,354 |
[
"chakra-core",
"ChakraCore"
] | Hi...I am using 1.11.12 version of chakracore (on Mac). Initially I've created release version of dylib, but it is crashing occasionally **(even with 1.11.15 version)**. (Also tried with release builds provided under 1.11.12 version of ChakraCore). The crash report is as follows:
int JsUtil::BaseDictionary<unsigned ... | generate release build symbol files on Mac | https://api.github.com/repos/chakra-core/ChakraCore/issues/6353/comments | 2 | 2019-12-12T13:51:22Z | 2020-03-25T10:32:01Z | https://github.com/chakra-core/ChakraCore/issues/6353 | 536,990,709 | 6,353 |
[
"chakra-core",
"ChakraCore"
] | Segmentation fault in libc.so.6 ispunct at ctype.c.
ubuntu 18.04.3
chakra (fd545b428de1a62e3de11962f76699a117bfc4df)
test.js
```javascript
eval(String.fromCodePoint(654321))
```
DebugInfo
```
* thread #1, name = 'ch', stop reason = signal SIGSEGV: address access protected (fault address: 0x7ffff72e94a2... | Segmentation fault in libc.so.6 ispunct at ctype.c | https://api.github.com/repos/chakra-core/ChakraCore/issues/6352/comments | 0 | 2019-12-12T10:06:13Z | 2019-12-12T10:06:13Z | https://github.com/chakra-core/ChakraCore/issues/6352 | 536,876,463 | 6,352 |
[
"chakra-core",
"ChakraCore"
] | When running the testcase below, a SyntaxError exception should be thrown while chakra does not.
According to ECMAScript Language Specification( from ES 5.1 to [ES 10](http://www.ecma-international.org/ecma-262/10.0/index.html#sec-for-statement) ), `for statement` should have a body with a type of `Statement`. This m... | An issue about for statement without body | https://api.github.com/repos/chakra-core/ChakraCore/issues/6351/comments | 13 | 2019-12-09T12:00:56Z | 2022-10-15T11:21:53Z | https://github.com/chakra-core/ChakraCore/issues/6351 | 534,883,891 | 6,351 |
[
"chakra-core",
"ChakraCore"
] | Optional chaining (https://github.com/tc39/proposal-optional-chaining) is now stage 4 and should be implemented; hopefully not too hard, roughly speaking:
```js
a?.someExpression;
//is sugar for
a ? a.someExpression : undefined;
```
I may try and do this in the next couple of weeks if no one else is. | Implement optional chaining | https://api.github.com/repos/chakra-core/ChakraCore/issues/6349/comments | 3 | 2019-12-05T17:24:36Z | 2020-12-22T23:06:41Z | https://github.com/chakra-core/ChakraCore/issues/6349 | 533,489,588 | 6,349 |
[
"chakra-core",
"ChakraCore"
] | I am using chakra library on Mac platform. I understand, ICU is for unicode support. Can someone explain what is the impact of excluding ICU from chakra library? Would there be any difference from functionality perspective? | impact of icu exclusion from chakra library | https://api.github.com/repos/chakra-core/ChakraCore/issues/6346/comments | 1 | 2019-12-04T06:31:25Z | 2020-03-25T08:15:13Z | https://github.com/chakra-core/ChakraCore/issues/6346 | 532,478,977 | 6,346 |
[
"chakra-core",
"ChakraCore"
] | the following js triggers a ICU_ASSERT in Js::IntlEngineInterfaceExtensionObject::EntryIntl_NormalizeLanguageTag
```
var intl=new Intl.DateTimeFormat('de-u-cu-eur-em-default-hc-h23-ks-level1-lb-strict-lw-normal-ms-metric-nu-latn-rg-atzzzz-sd-atat1-ss-none-tz-atvie-va-posix');
``` | ICU_ASSERT in Js::IntlEngineInterfaceExtensionObject::EntryIntl_NormalizeLanguageTag | https://api.github.com/repos/chakra-core/ChakraCore/issues/6345/comments | 0 | 2019-12-03T08:58:55Z | 2019-12-03T08:58:55Z | https://github.com/chakra-core/ChakraCore/issues/6345 | 531,826,772 | 6,345 |
[
"chakra-core",
"ChakraCore"
] | the following js fragment can cause a null pointer dereference in SCCLiveness::ProcessStackSymUse
```
function func(){}
class C{}
for (var i=0;i++<1000;i++){
func(new C(this.__defineGetter__("x",()=>{})),C);
}
``` | null pointer dereference in SCCLiveness::ProcessStackSymUse | https://api.github.com/repos/chakra-core/ChakraCore/issues/6344/comments | 0 | 2019-12-03T07:30:30Z | 2019-12-03T07:30:30Z | https://github.com/chakra-core/ChakraCore/issues/6344 | 531,783,156 | 6,344 |
[
"chakra-core",
"ChakraCore"
] | the following js fragment cause a null pointer dereference in TryGetCallbackDefInstr
```
function f1(f2) {
for(var i=0;i<null;f2());
}
function f() {
f1.call(()=>{});
};
for (var i=0;i<1000;i++)
f();
``` | null pointer dereference in TryGetCallbackDefInstr | https://api.github.com/repos/chakra-core/ChakraCore/issues/6343/comments | 0 | 2019-12-03T07:14:33Z | 2019-12-03T07:14:33Z | https://github.com/chakra-core/ChakraCore/issues/6343 | 531,776,093 | 6,343 |
[
"chakra-core",
"ChakraCore"
] | When using `Object.getOwnPropertyDescriptor` to get the descriptor of `regex.source` and `regex.__proto__.source`, I find the property is not defined in RegExp.prototype. According to ES6 and ES10, this property belongs to RegExp.prototype. And the property has been changed into accessor property since ES6. Maybe this ... | Incorrect realization of RegExp.prototype.source | https://api.github.com/repos/chakra-core/ChakraCore/issues/6342/comments | 1 | 2019-12-03T02:08:31Z | 2020-03-25T08:52:56Z | https://github.com/chakra-core/ChakraCore/issues/6342 | 531,662,346 | 6,342 |
[
"chakra-core",
"ChakraCore"
] | When I execute the testcase below, the returncode is -6 and aborted without other information (exception, warning, OOM etc.) provided. This is not friendly enough for users. Maybe you could enhance it.
#### version
[eaaf7ac](https://github.com/microsoft/ChakraCore/commit/eaaf7ac6beca01ab0d80c05959f3868463043c2d)
##... | A question about infinity string | https://api.github.com/repos/chakra-core/ChakraCore/issues/6340/comments | 4 | 2019-11-30T09:09:42Z | 2019-12-03T02:19:05Z | https://github.com/chakra-core/ChakraCore/issues/6340 | 530,553,862 | 6,340 |
[
"chakra-core",
"ChakraCore"
] | The current error message for `import` or `export` encountered in non-module (script) code is:
```
SyntaxError: Module import or export statement unexpected here
```
This is rather vague and it's not immediately obvious that "here" means "anywhere in non-module code". The error message could be improved, I think... | Improve error for import/export in non-ESM code | https://api.github.com/repos/chakra-core/ChakraCore/issues/6339/comments | 1 | 2019-11-28T23:45:09Z | 2019-12-06T06:50:46Z | https://github.com/chakra-core/ChakraCore/issues/6339 | 530,101,568 | 6,339 |
[
"chakra-core",
"ChakraCore"
] | When calling `Reflect.construct` with an argument list, the members of the argument list are corrupted.
> console.log(navigator.userAgent)
Mozilla/5.0 (Windows NT 10.0; Win64; x64) ... Edge/18.17763
> var subject = [];
> console.log(subject.__proto__ === Array.prototype);
true
>... | Reflect.construct corrupts members of the arguments list (error 80020101) | https://api.github.com/repos/chakra-core/ChakraCore/issues/6338/comments | 3 | 2019-11-28T13:04:03Z | 2020-04-10T14:44:29Z | https://github.com/chakra-core/ChakraCore/issues/6338 | 529,901,110 | 6,338 |
[
"chakra-core",
"ChakraCore"
] | Hi..I am getting a rare crash in JsRun function on macOs. Since it is rare, I am facing problem reproducing it in order to find its root-cause. Could you please suggest what can cause this crash?
`int JsUtil::BaseDictionary<unsigned long, SourceContextInfo*, Memory::Recycler, DictionarySizePolicy<PowerOf2Policy, 2... | rare crash of JsRun function on Mac | https://api.github.com/repos/chakra-core/ChakraCore/issues/6337/comments | 2 | 2019-11-27T14:49:08Z | 2019-11-29T04:52:44Z | https://github.com/chakra-core/ChakraCore/issues/6337 | 529,393,618 | 6,337 |
[
"chakra-core",
"ChakraCore"
] | how to compile it by armv7-linux-gnueabi-gcc | how to compile it by armv7-linux-gnueabi-gcc | https://api.github.com/repos/chakra-core/ChakraCore/issues/6335/comments | 1 | 2019-11-25T03:48:36Z | 2020-05-15T19:30:50Z | https://github.com/chakra-core/ChakraCore/issues/6335 | 527,826,152 | 6,335 |
[
"chakra-core",
"ChakraCore"
] | ```
function foo(){
try{
x = arguments;
throw Error();
} catch(e){
return x.length;
}
var x = {};
}
for(var v0 = 0; v0 < 0x1000; v0++){
foo();
}
```
It is related to #6058 .
ChakraCore Version: ch version 1.11.15.0 (1B6EE856A9F07071BB8D11ED9068CF262DF8285FC9E762E9F77FBB6A3957E... | Null pointer dereference in ValueType::FromObject() when jitting | https://api.github.com/repos/chakra-core/ChakraCore/issues/6333/comments | 0 | 2019-11-19T15:39:45Z | 2019-11-19T15:39:45Z | https://github.com/chakra-core/ChakraCore/issues/6333 | 525,089,298 | 6,333 |
[
"chakra-core",
"ChakraCore"
] | The following JavaScript code can lead to a null pointer de-reference.
```
function test(){
var v1 = 0;
for(var v2 = 0;;v2++){
for(var v3 = 0;;v3++){
v1 = v3;
}
}
}
test()
```
It is related to #5532 .
ChakraCore Version: ch version 1.11.15.0 (1B6EE856A9F07071BB8D11ED9068CF262DF828... | Null pointer dereference in EmitBooleanExpression | https://api.github.com/repos/chakra-core/ChakraCore/issues/6332/comments | 0 | 2019-11-19T09:46:39Z | 2019-11-19T15:41:55Z | https://github.com/chakra-core/ChakraCore/issues/6332 | 524,891,928 | 6,332 |
[
"chakra-core",
"ChakraCore"
] | Are there any plans to publish version 1.12 on Nuget in the foreseeable future? | Plans to release 1.12? | https://api.github.com/repos/chakra-core/ChakraCore/issues/6329/comments | 1 | 2019-11-12T19:11:48Z | 2020-03-25T08:21:01Z | https://github.com/chakra-core/ChakraCore/issues/6329 | 521,746,924 | 6,329 |
[
"chakra-core",
"ChakraCore"
] | PoC:
```
var b = 0
function test0() {
var a = 100;
for (var i = 1; (a |= 1) && i < 6; ++i) {
test0a();
for (var j = 0; j < 1; ++j) {
a = 0xffffffffff
for (var k = 0; k < 1; ++k) {
i = a;
+i;
}
}
print(i) // i should be 1099511627775 (0xffffffffff) ... | Type confusion between integer and float in JIT | https://api.github.com/repos/chakra-core/ChakraCore/issues/6325/comments | 1 | 2019-11-05T21:44:35Z | 2020-04-11T06:22:25Z | https://github.com/chakra-core/ChakraCore/issues/6325 | 518,060,886 | 6,325 |
[
"chakra-core",
"ChakraCore"
] | I discovered this while trying to produce a repro for #6160. The following code when run in `ch` hits an assertion in `InlineCache.cpp`:
```js
WScript.Attach(() => {
let iter = g();
iter.next();
iter.next();
});
(async () => {
await 777;
await 1206;
WScript.Detach(() => {});
})();
... | Assertion failure in InlineCache.cpp | https://api.github.com/repos/chakra-core/ChakraCore/issues/6323/comments | 5 | 2019-11-04T15:50:41Z | 2020-06-09T03:07:53Z | https://github.com/chakra-core/ChakraCore/issues/6323 | 517,240,598 | 6,323 |
[
"chakra-core",
"ChakraCore"
] | The documentation for `JsRunScript` function at https://github.com/microsoft/ChakraCore/wiki/JsRunScript doesn't really tell much about allowed values (including the null pointer) and their interpretation for the `sourceUrl` argument:
> sourceUrl: The location the script came from.
Scripts do not always come from... | Insufficient documentation for the `sourceUrl` argument to the `JsRunScript` function | https://api.github.com/repos/chakra-core/ChakraCore/issues/6322/comments | 3 | 2019-11-03T14:54:09Z | 2019-11-03T17:22:15Z | https://github.com/chakra-core/ChakraCore/issues/6322 | 516,839,549 | 6,322 |
[
"chakra-core",
"ChakraCore"
] | The Wiki says JsCreateRuntime takes 4 arguments: https://github.com/microsoft/ChakraCore/wiki/JsCreateRuntime
This seems to apply to the frozen IE11 JSRT mode. The edge-mode version of the function takes 3 arguments, why doesn't the Wiki reflect that at all? | Is the Wiki outdated? | https://api.github.com/repos/chakra-core/ChakraCore/issues/6321/comments | 2 | 2019-11-03T13:14:53Z | 2019-11-03T16:38:03Z | https://github.com/chakra-core/ChakraCore/issues/6321 | 516,826,229 | 6,321 |
[
"chakra-core",
"ChakraCore"
] | ```js
function opt1() {
}
function opt(obj) {
Array.prototype.push.call(obj, 1);
opt1(' ' + obj);
}
var arr = new Array([0]);
for (let i = 0; i < 0x100; i++) {
opt(arr[0]);
}
opt(2.3023e-320);
```
backtrace is
```
[----------------------------------registers------------------------... | SegmentFault due to a type confusion bug in JavascriptNativeIntArray::Push | https://api.github.com/repos/chakra-core/ChakraCore/issues/6320/comments | 0 | 2019-11-01T06:58:02Z | 2019-11-25T22:53:44Z | https://github.com/chakra-core/ChakraCore/issues/6320 | 515,945,328 | 6,320 |
[
"chakra-core",
"ChakraCore"
] | When throwing an error using JsSetException inside a for..of loop error.stack does point to the last line of the for loop instead of the line which has caused the real exception.
for..in however does work properly
throwing inside JavaScript works properly even inside for..of loop
try..catch and rethrow works prope... | Wrong stack trace in errors shown in combination of for..of loops and JsSetException | https://api.github.com/repos/chakra-core/ChakraCore/issues/6314/comments | 6 | 2019-10-28T08:15:55Z | 2020-03-26T22:45:05Z | https://github.com/chakra-core/ChakraCore/issues/6314 | 513,156,670 | 6,314 |
[
"chakra-core",
"ChakraCore"
] | The following case triggers assertion failure.
```js
(function foo() {
function bar() {
foo;
}
with (1) foo();
})();
```
```
ASSERTION 20300: (E:\ChakraCore\lib\Runtime\Language\InterpreterStackFrame.cpp, line 7558) scopeSlotCount != 0
Failure: (scopeSlotCount != 0)
FATAL ERROR: ch.exe ... | ASSERTION Failure: (scopeSlotCount != 0) | https://api.github.com/repos/chakra-core/ChakraCore/issues/6313/comments | 0 | 2019-10-28T03:33:32Z | 2019-10-28T03:33:32Z | https://github.com/chakra-core/ChakraCore/issues/6313 | 513,078,826 | 6,313 |
[
"chakra-core",
"ChakraCore"
] | ```
var count = 0;
var myEval = eval;
function foo(){
myEval("var v" + count++);
var y;
}
for(i = 0, v0 = 0; i < 100000; i += count, v0 += 400){
new foo(v0);
}
```
platform: Ubuntu 18.04.3 LTS
version: ChakraCore 1.12.0
commit hash: 39078423036150a32059b315ff4d7e8d2cbced87 (Date: Wed Oct 9 15:40... | Segfault due to JIT is causig bad code gen in SCCLiveness::ProcessStackSymUse | https://api.github.com/repos/chakra-core/ChakraCore/issues/6311/comments | 0 | 2019-10-23T01:37:57Z | 2019-10-23T01:37:57Z | https://github.com/chakra-core/ChakraCore/issues/6311 | 511,019,039 | 6,311 |
[
"chakra-core",
"ChakraCore"
] | The debug build of Chakacore crashes.
ch version 1.11.13.0
```javascript
function main() {
let v1 = "A";
do {} while (0 != v1);
}
main();
```
| Assertion failure in ib/Backend/BackwardPass.cpp, line 2511 | https://api.github.com/repos/chakra-core/ChakraCore/issues/6310/comments | 1 | 2019-10-16T05:05:57Z | 2019-10-28T19:11:27Z | https://github.com/chakra-core/ChakraCore/issues/6310 | 507,616,490 | 6,310 |
[
"chakra-core",
"ChakraCore"
] | Relates to https://github.com/Homebrew/homebrew-core/pull/45033
Trying to `ChakraCore` from `v1.11.13` to `v1.11.14`, but receiving these errors:
```
/tmp/chakra-20191009-92499-1eshv12/ChakraCore-1.11.14/lib/Backend/amd64/LinearScanMdA.S:54:34: error: unknown token in expression
movups xmmword ptr [rax + 80... | chakra 1.11.15 compilation issue | https://api.github.com/repos/chakra-core/ChakraCore/issues/6309/comments | 8 | 2019-10-14T00:04:56Z | 2020-01-04T19:07:58Z | https://github.com/chakra-core/ChakraCore/issues/6309 | 506,400,777 | 6,309 |
[
"chakra-core",
"ChakraCore"
] | I think that ES6 unicode mode may not be implemented 100% correctly (or maybe v8 has it wrong):
```js
print(/\udf06/u.test('\ud834\udf06'));
```
eshost results:
```
#### V8 --harmony
false
#### Chakra
true
#### JavaScriptCore
true
#### chDev
true
#### SpiderMonkey
false
```
V8 and SpiderMon... | RegExp Unicode matching difference to v8 | https://api.github.com/repos/chakra-core/ChakraCore/issues/6308/comments | 1 | 2019-10-13T22:44:39Z | 2020-03-25T08:17:59Z | https://github.com/chakra-core/ChakraCore/issues/6308 | 506,392,405 | 6,308 |
[
"chakra-core",
"ChakraCore"
] | This `test.js` can trigger null pointer dereference .
run `ch.exe -bgjit- test.js`
```javascript
const v4 = [13.37, 13.37];
function v8() {
const v15 = Math.round(Infinity);
try {
v8();
const v19 = new Uint32Array();
const v20 = typeof v19;
} catch (v20) {
v4.d... | null pointer dereference in JavascriptExceptionOperators::OP_TryCatch | https://api.github.com/repos/chakra-core/ChakraCore/issues/6307/comments | 2 | 2019-10-11T08:04:52Z | 2019-10-11T22:21:49Z | https://github.com/chakra-core/ChakraCore/issues/6307 | 505,701,575 | 6,307 |
[
"chakra-core",
"ChakraCore"
] | let buggy = [1.1, {}, {}];
buggy.__proto__ = new Proxy([], buggy);
buggy[0] = 5.5627483035514150e-309; | Out of stack space | https://api.github.com/repos/chakra-core/ChakraCore/issues/6306/comments | 2 | 2019-10-10T03:32:22Z | 2020-03-25T08:28:14Z | https://github.com/chakra-core/ChakraCore/issues/6306 | 505,011,458 | 6,306 |
[
"chakra-core",
"ChakraCore"
] | ````
var A = new Uint32Array(10000);
function foo()
{
for (var i = 0; i < 10000; i++) {
A[i] = 0x1234;
}
for (var i = 0; i < 10000; i++)
{
A[i] = foo;
}
}
var r;
for (var i = 0; i < 1000; i++)
{
print(i);
r = foo();
}
```` | DebugBreak in ThreadContext::AssertJsReentrancy | https://api.github.com/repos/chakra-core/ChakraCore/issues/6305/comments | 0 | 2019-10-09T09:58:28Z | 2019-10-09T09:58:28Z | https://github.com/chakra-core/ChakraCore/issues/6305 | 504,543,169 | 6,305 |
[
"chakra-core",
"ChakraCore"
] | ````
var array = Array();
for (var i = 0; i < 40000; ++i)
array[i] = i;
function test()
{
var src = 'var x=/';
src += array.join(function(){})+'/;';
eval(src);
}
test();
```` | DebugBreak in Js::GlobalObject::DefaultEvalHelper | https://api.github.com/repos/chakra-core/ChakraCore/issues/6304/comments | 0 | 2019-10-09T09:39:10Z | 2019-10-09T09:39:10Z | https://github.com/chakra-core/ChakraCore/issues/6304 | 504,532,408 | 6,304 |
[
"chakra-core",
"ChakraCore"
] | the callApplyId of function foo didn't get profiled.
````
function main() {
for (;;Array.prototype.sort.call(main,()=>{})()++){}
Array.prototype.sort.call(main,()=>{});
}
main();
```` | callApplyId didn't get profiled | https://api.github.com/repos/chakra-core/ChakraCore/issues/6303/comments | 0 | 2019-10-09T08:43:08Z | 2019-11-20T18:51:59Z | https://github.com/chakra-core/ChakraCore/issues/6303 | 504,502,155 | 6,303 |
[
"chakra-core",
"ChakraCore"
] | Stage 3 proposal: https://github.com/tc39/proposal-promise-any
Note that this includes `AggregateError` as well. | Implement Promise.any and AggregateError | https://api.github.com/repos/chakra-core/ChakraCore/issues/6299/comments | 0 | 2019-10-04T06:35:38Z | 2021-04-21T14:00:31Z | https://github.com/chakra-core/ChakraCore/issues/6299 | 502,456,114 | 6,299 |
[
"chakra-core",
"ChakraCore"
] | The proposal reached stage 3 at today’s TC39 meeting.
Repository: https://github.com/tc39/proposal-string-replaceall | Implement String.prototype.replaceAll | https://api.github.com/repos/chakra-core/ChakraCore/issues/6297/comments | 6 | 2019-10-02T15:57:03Z | 2020-03-25T23:03:55Z | https://github.com/chakra-core/ChakraCore/issues/6297 | 501,579,858 | 6,297 |
[
"chakra-core",
"ChakraCore"
] | See #6295
When parsing modules, we are currently building the list of dependency specifiers in reverse source-code order (by using `list->Prepend`), and we are somehow dependent on that reverse order.
Investigate whether we can build the list in the correct order from the start. | Refactor module code to keep dependency specifiers in source code order | https://api.github.com/repos/chakra-core/ChakraCore/issues/6296/comments | 1 | 2019-09-27T16:45:03Z | 2021-02-13T15:11:28Z | https://github.com/chakra-core/ChakraCore/issues/6296 | 499,544,664 | 6,296 |
[
"chakra-core",
"ChakraCore"
] | hi, thank you for sharing .
I have two questions :
1、I hope to add a JsDisposeContext API , it 's important just like JsDisposeRuntime .
2、report a error , that is a error of division by zero , js syntax doesn't display error , and result is zero . | I hope to add a JsDisposeContext API . | https://api.github.com/repos/chakra-core/ChakraCore/issues/6291/comments | 4 | 2019-09-22T00:22:35Z | 2020-03-25T08:25:03Z | https://github.com/chakra-core/ChakraCore/issues/6291 | 496,716,347 | 6,291 |
[
"chakra-core",
"ChakraCore"
] | 
| Computer virus include Exp.CVE-2016-3377 | https://api.github.com/repos/chakra-core/ChakraCore/issues/6289/comments | 1 | 2019-09-19T08:06:39Z | 2019-10-09T22:54:06Z | https://github.com/chakra-core/ChakraCore/issues/6289 | 495,639,562 | 6,289 |
[
"chakra-core",
"ChakraCore"
] | SpiderMonkey throws an early error in the following case:
```js
function f() {}
function g() { 'use strict'; if (false) f() = 1; }
```
whereas CC and V8 do not. Should we throw early as well? | Should we throw an early error for function calls on LHS in strict mode? | https://api.github.com/repos/chakra-core/ChakraCore/issues/6283/comments | 4 | 2019-09-12T17:34:26Z | 2019-09-13T21:49:32Z | https://github.com/chakra-core/ChakraCore/issues/6283 | 492,937,978 | 6,283 |
[
"chakra-core",
"ChakraCore"
] | Wrong Realization of Function.length by ChakraCore
```js
function func01(a, b) {
return a + b
}
print(func01.length)
Object.defineProperty(func01, "length", {
writable: true
})
func01.length = "0x1234"
print(func01.length)
```
the expected output: `2`<--Number ,`0x1234`<--String
ChakraCore output... | Wrong Realization of Function.length | https://api.github.com/repos/chakra-core/ChakraCore/issues/6282/comments | 1 | 2019-09-12T06:16:37Z | 2019-09-12T17:31:08Z | https://github.com/chakra-core/ChakraCore/issues/6282 | 492,606,952 | 6,282 |
[
"chakra-core",
"ChakraCore"
] | ### Version: [8fcb0f1](https://github.com/microsoft/ChakraCore/commit/8fcb0f1b5771fe8db855e85d7bf7c73c5d32c386), [ChakraCore v1.11.12](https://github.com/microsoft/ChakraCore/releases/tag/v1.11.12)
### Testcase:
````
var NISLFuzzingFunc = function(a, b, c) {
[11] += a[11];
};
````
### Command:
````
./Chak... | SyntaxError should be thrown during the parsing | https://api.github.com/repos/chakra-core/ChakraCore/issues/6278/comments | 0 | 2019-09-10T09:39:02Z | 2019-09-12T17:47:51Z | https://github.com/chakra-core/ChakraCore/issues/6278 | 491,562,038 | 6,278 |
[
"chakra-core",
"ChakraCore"
] | The debug build of Chakacore crashes.
PoC:
```
function inlinee() {
Number.isSafeInteger(1.1 * 0);
return inlinee.arguments[0];
}
function opt(convert_to_var_array) {
let stack_arr = [];
stack_arr[20] = 1.1;
stack_arr[10000] = 1.1;
stack_arr[20000] = 2.2;
let heap_arr = inlinee(stack_arr);
... | ASSERTION failure in ChakraCore/lib/Runtime/Library/JavascriptArray.cpp, line 11954 | https://api.github.com/repos/chakra-core/ChakraCore/issues/6277/comments | 1 | 2019-09-10T04:47:03Z | 2019-10-01T21:01:25Z | https://github.com/chakra-core/ChakraCore/issues/6277 | 491,447,707 | 6,277 |
[
"chakra-core",
"ChakraCore"
] | The debug build of Chakracore crashes
PoC:
```
var arr = [0, 1, 2, 3, 4, 5, 6, 7];
Array.prototype.push.apply(arr, []);
```
Version= v1.11.12
OS=Ubuntu 16.04.6
Arch=x86_64 | Crash due to memory corruption in Js::JavascriptNativeIntArray::ValidateArray | https://api.github.com/repos/chakra-core/ChakraCore/issues/6276/comments | 0 | 2019-09-10T04:34:14Z | 2019-09-10T04:34:14Z | https://github.com/chakra-core/ChakraCore/issues/6276 | 491,444,559 | 6,276 |
[
"chakra-core",
"ChakraCore"
] | The debug and release build of Chakracore crashes
PoC:
```
var dnaInput = ">ONE Homo sapiens alu\n\
GGCCGGGCGCGGTGGCTCACGCCTGTAATCCCAGCACTTTGGGAGGCCGAGGCGGGCGGA\n\
TCACCTGAGGTCAGGAGTTCGAGACCAGCCTGGCCAACATGGTGAAACCCCGTCTCTACT\n\
gagatacctttgcaattttt\n";
dnaInput = dnaInput + dnaInput + dnaInput + dnaInput + dnaIn... | Crash due to buffer overrun in UnifiedRegex::RuntimeCharTrie::CloneFrom | https://api.github.com/repos/chakra-core/ChakraCore/issues/6275/comments | 0 | 2019-09-10T04:27:41Z | 2019-09-26T02:44:07Z | https://github.com/chakra-core/ChakraCore/issues/6275 | 491,443,000 | 6,275 |
[
"chakra-core",
"ChakraCore"
] | The debug and release build of Chakracore crashes
PoC:
```
function foo(f) {
f(f);
}
function bar(f) {
new foo(f);
}
bar(function () {
foo(bar);
});
```
Version= v1.11.12
OS=Ubuntu 16.04.6
Arch=x86_64 | Crash due to buffer overrun in Inline::BuildIRForInlinee | https://api.github.com/repos/chakra-core/ChakraCore/issues/6274/comments | 0 | 2019-09-10T04:04:29Z | 2019-09-10T04:25:33Z | https://github.com/chakra-core/ChakraCore/issues/6274 | 491,437,747 | 6,274 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.