node doesn't execute JS script and exits silently

[stas-neverov]

• Version: 4.4.7, 4.5.0 (no longer reproduces on 4.6.0)
• Platform: Windows 10 x64 Enterprise edition (build 10240)
• Subsystem: n/a

Hi,

I've got an issue running node v4.4.7 on one particular machine. It's a Windows 10 tablet with pre-release version of Goldmont CPU. So the issue could be caused by unsupported HW.

Whatever script I give it to execute, node silently exits without executing the script.

Node.exe binary was downloaded from https://nodejs.org/dist/v4.4.7/win-x64/

test.js:
console.log('test');

When I ran it like this:
node test.js
it exits without any errors and without console output. Didn't find anything in Windows event logs either.

Also tried:
node debug test.js
same result.

Version and command line help are printed fine:
node -v
v4.4.7

Tested with 4.5.0 - same result.
But with 4.6.0 everything works fine. Though I do not see any 4.6.0 release notes that could be related to the issue like this.

How could I further troubleshoot the issue? This time I'm lucky since 4.6.0 was released the next day I saw the issue with 4.4.7. But not seeing anything relevant in the release notes makes me think that I can see such behavior again, maybe on different hardware.

[bnoordhuis]

Your best bet probably is to attach a native debugger. The only substantive change between v4.5.0 and v4.6.0 was the openssl upgrade and disabling support for obsolete openssl HW engines.

The openssl PRNG is used to seed Math.random() at startup. I'd say that is the most likely culprit. EDIT: Or maybe openssl's CPU feature detection.

[stas-neverov]

For v4.5.0 debugger shows access violation (c0000005) @
node!sha1_block_data_order_shaext(void)+0x2a3 [c:\ws\deps\openssl\asm\x64-win32-masm\sha\sha1-x86_64.asm @ 1435]

The issue was fixed in openssl v1.0.2i:
https://rt.openssl.org/Ticket/Display.html?id=4530
openssl/openssl@7123aa8

The issue was CPU specific.