[GH-ISSUE #388] Segmentation fault on M1 #73

Closed
opened 2026-03-03 13:52:47 +03:00 by kerem · 4 comments
Owner

Originally created by @beautyfree on GitHub (Apr 1, 2025).
Original GitHub issue: https://github.com/jehna/humanify/issues/388

Maybe the reason https://github.com/withcatai/node-llama-cpp/issues/211

Originally created by @beautyfree on GitHub (Apr 1, 2025). Original GitHub issue: https://github.com/jehna/humanify/issues/388 Maybe the reason https://github.com/withcatai/node-llama-cpp/issues/211
kerem closed this issue 2026-03-03 13:52:47 +03:00
Author
Owner

@beautyfree commented on GitHub (Apr 1, 2025):

tried to download same llama.cpp as used for quantilization:

npx node-llama-cpp source download --release "b1350"

but it ended with error:

✖️ Failed to compile llama.cpp
Failed to build llama.cpp with Metal support.
<!-- gh-comment-id:2770819868 --> @beautyfree commented on GitHub (Apr 1, 2025): tried to download same llama.cpp as used for quantilization: ``` npx node-llama-cpp source download --release "b1350" ``` but it ended with error: ``` ✖️ Failed to compile llama.cpp Failed to build llama.cpp with Metal support. ```
Author
Owner

@0xdevalias commented on GitHub (Apr 2, 2025):

@beautyfree I see you closed this; does that mean you resolved your issue? If so, do you mind sharing what the solution was in case others run into similar in future.

<!-- gh-comment-id:2773030820 --> @0xdevalias commented on GitHub (Apr 2, 2025): @beautyfree I see you closed this; does that mean you resolved your issue? If so, do you mind sharing what the solution was in case others run into similar in future.
Author
Owner

@beautyfree commented on GitHub (Apr 2, 2025):

It was deep research for me with cutting code that can throw error and I found out that the reason in webcrack library which uses isolated-vm

If you getting error like this try to prepend your cli command with NODE_OPTIONS=--no-node-snapshot

<!-- gh-comment-id:2773044613 --> @beautyfree commented on GitHub (Apr 2, 2025): It was deep research for me with cutting code that can throw error and I found out that the reason in webcrack library which uses isolated-vm If you getting error like this try to prepend your cli command with `NODE_OPTIONS=--no-node-snapshot`
Author
Owner

@0xdevalias commented on GitHub (Apr 12, 2025):

If you getting error like this try to prepend your cli command with NODE_OPTIONS=--no-node-snapshot

Linking to the relevant docs for future reference:

<!-- gh-comment-id:2798387568 --> @0xdevalias commented on GitHub (Apr 12, 2025): > If you getting error like this try to prepend your cli command with `NODE_OPTIONS=--no-node-snapshot` Linking to the relevant docs for future reference: - https://github.com/laverdet/isolated-vm#requirements - > 🚨 If you are using a version of nodejs `20.x` or later, you must pass `--no-node-snapshot` to `node`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/humanify#73
No description provided.