We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mksnapshot is used as part of building/compiling node. However, the build fails on mksnapshot command below:
LD_LIBRARY_PATH=/home/shared/downloads/node/out/Release/lib.host:/home/shared/downloads/node/out/Release/lib.target:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd ../tools/v8_gypfiles; mkdir -p /home/shared/downloads/node/out/Release/obj.target/v8_snapshot/geni; "/home/shared/downloads/node/out/Release/mksnapshot" --turbo_instruction_scheduling "--target_os=openbsd" "--target_arch=arm64" --startup_src "/home/shared/downloads/node/out/Release/obj.target/v8_snapshot/geni/snapshot.cc" --embedded_variant Default --embedded_src "/home/shared/downloads/node/out/Release/obj.target/v8_snapshot/geni/embedded.S" --no-native-code-counters
The error:
# # Fatal javascript OOM in MemoryChunk allocation failed during deserialization. # Trace/BPT trap
How to debug this error. It seems it fails on OOM even before asking for memory. Is there a way to trace which call it failed on?
The text was updated successfully, but these errors were encountered:
Posted this issue on node repo as well: nodejs/node#43444
Sorry, something went wrong.
No branches or pull requests
mksnapshot is used as part of building/compiling node. However, the build fails on mksnapshot command below:
The error:
How to debug this error. It seems it fails on OOM even before asking for memory. Is there a way to trace which call it failed on?
The text was updated successfully, but these errors were encountered: