Node.js compilation for Windows x86 target architecture fails with code -1073741819

[vladimir-andreevich]

I have encountered troubles while building Node.js on 64-bit Microsoft Windows 19044.2728. The x64 executable and x64 MSI installer are built successfully. However, when I try to build Node.js for x86 target architecture, the system after some time of compilation outputs the following error:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(241,5): error MSB8066: Custom build for 'out\Release\\mkcodecache.exe;out\Release\\node_mksnapshot.exe' exited with code -1073741819. [node-14.19.3\node.vcxproj]
I performed a search and did not manage to find much information about this specific problem. Could you help to resolve this issue?

[balshaer]

You may want to consider checking your environment variables, Visual Studio installation, and Node.js source code for any potential issues. It would also be helpful to run a memory diagnostic tool to identify any memory-related problems. Additionally, disabling antivirus software may help resolve the error. If the problem persists, you may want to try using a different version of Visual Studio.

[vladimir-andreevich]

I have no idea why it happens. Disabled the antivirus, fully repaired Visual Studio, launched the command line as an administrator. The error is not gone. NetWide Assembler is installed in the default location, no need to modify PATH.

[subtly-sms]

Is it possibly a linking issue similar to the one described with fipsinstall: nodejs/node#45465?

Both are related to the node_mksnapshot.exe and Windows 10.

[vladimir-andreevich]

I checked the issue and made additional research. It is unlikely that the issue happens because of FIPS. Error -1073741819 is commonly associated with a runtime error or access violation. However, the system does not specify where exactly the error occurs and why this error occurs. Is there a way to discover it with debug tools?

[bnoordhuis]

-1073741819 is 0xC0000005 is Access Violation, i.e., most likely a null or bad pointer dereference. Try building v14.21.3 instead (or the latest v16.x or v18.x); you may be hitting a bug that's already been fixed.

[bnoordhuis]

Look up the node_mksnapshot invocation in the sln file and run that directly under your debugger. You can also piece it together from the node.gyp file in the top-level directory.

[vladimir-andreevich]

It took me a while to make it. If launched separately with the command msbuild node_mksnapshot.vcxproj /m:2 /t:"Build" /p:Configuration=Release /p:Platform=Win32, node_mksnapshot builds successfully for Windows x86 target architecture. The error occurs only during the whole application build. This is what LLDB shows me when I attach it to the MSBuild process while building Node.js with the command vcbuild.bat release x86 msi:

lldb_msbuild.txt

I hope this information is helpful.

[bnoordhuis]

It's devoid of details, I'm afraid. Not through any fault of yours, the stack frames simply aren't there.

My hunch is that it's crashing in the machine code that V8 emits because that uses a calling convention that C++ debuggers don't understand. Such bugs are unfortunately very hard to debug.

[vladimir-andreevich]

I believe this case needs further investigation. Do you need any additional information while I can still reproduce the issue?

[bnoordhuis]

Support for x86 Windows was demoted to experimental status a while ago, meaning: we accept fixes but don't expect anyone to investigate.