build with error `Command failed with signal "SIGSEGV"`.
See original GitHub issueWhen I use docusaurus-search-local to build my document static site, it raise an error without any more information even if I set DEBUG=search-local:*.
Env
- OS: Linux docker
- Arch: amd64
- docusaurus-search-local: 0.14.2
- nodejieba: 2.5.1
- node: 4.15.3
Steps
- clone my document project https://github.com/hpcde/cluster-docs and checkout to commit “e74db1218a0607a28d07f998b20355f00bc99b79” if possible.
- run
docker run -it --rm -v ${PWD}:/root/p --entrypoint ash node:14.15.3-alpine3.12 - In docker container, run:
cd /root/p
yarn install
USE_LOCAL_SEARCH=ON yarn build
than there is an error like:
✔ Client
Compiled successfully in 28.20s
✔ Server
Compiled successfully in 33.53s
error Command failed with signal "SIGSEGV".
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
But, if I disable docusaurus-search-local plugin (just run yarn build), everything works fine.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Next.js - yarn dev: error Command failed with signal "SIGSEGV"
In order to get it working on my environment, I am using Docker with following parameters: docker buildx build --platform linux/amd64 .
Read more >SIGSEGV: Linux Segmentation Fault | Signal 11, Exit code 139
In Unix/Linux, SIGSEGV is operating system signal 11; In Docker containers, when a Docker container terminates due to a SIGSEV error, it throws...
Read more >command failed due to signal: segmentation fault: 11
It came up with an error, "command failed due to signal: segmentation fault: 11". I have been looking on the internet for fixes...
Read more >Segmentation Fault in Linux Containers (exit code 139)
The SIGSEGV Linux signal denotes a segmentation violation within a running process. Segmentation errors occur when a program tries to access memory that ......
Read more >Error :”Received signal SIGSEGV.” - Ansys Learning Forum
The fluent successfully compile the UDF. There is 1 warning though but the simulations run perfectly fine with the expected results. The warning...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This seems to be a known issue.
I have reproduced the problem. And I also tried to downgrade nodejieba to v2.4.2, It builds successfully. So you can pin nodejieba in your package.json to
2.4.2(without^), until nodejieba (or CppJieba) fixed the issue.Fixed by downgrading nodejieba to v2.4.2. Thanks for your nice and patient reply👍!