Kunal Pathak

I will come up with a code when I get chance.

Currently for non-win32, chakracore is always built using [Release](https://github.com/nodejs/node-chakracore/blob/xplat/deps/chakrashim/chakracore.gyp#L15). Address to build the flavor based on what was passed to `./configure`.

@morkai , Regading crash on Windows 7, similar issue was recently reported at Microsoft/chakracore#212 and was fixed with Microsoft/chakracore#202. Just to make sure that this is same issue, could you...

Thanks for confirming @morkai . The latest [release](https://github.com/Microsoft/node/releases/tag/node-chakracore-6.0.0-pre3) should unblock you from using `Node.js with chakracore` on Windows 7 machine. We are investigating the performance issue you reported and will...

@morkai , after investigating this for sometime, it seems that the slowness in node+chakracore is happening because of JIT optimization that we don't do for `arguments`. See Microsoft/Chakracore#313 for details....

Thanks @abodalevsky for reporting. We will investigate.

Below test cases are failing as well and root case seems to be same. The script engine is in exception state and host tries to allocate string which returns error....

Thanks for the interest @yunong. You could use [windbg](https://msdn.microsoft.com/en-us/library/windows/hardware/ff551063%28v=vs.85%29.aspx) to debug dump from node+chakracore. You could track unexpected crashes and memory leaks with it. An example of bug in node-serialport...

> Some recent changes caused hard coded v8.h: Seems that it was [hard coded](https://github.com/nodejs/node-chakracore/blob/nodejs-chakracore/node.gyp#L188) from day 1. I will look into it to see what can be done.

Thanks @Iscgx for reporting. We will take a look into it and update what is going on.