cargo build --release -p bytehound-cli errors

[harlanc]

cargo build --release -p bytehound-cli

encounter the following errors:

Compiling server-core v0.8.0 (/data1/workspace/bytehound/server-core)
ror: failed to run custom build command for `server-core v0.8.0 (/data1/workspace/bytehound/server-core)`

used by:

process didn't exit successfully: `/data1/workspace/bytehound/target/release/build/server-core-b124e777852b75e3/build-script-build` (exit status: 101)
--- stdout
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/.babelrc
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/node_modules
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/package.json
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/PageDataList.js
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/utils.js
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/App.js
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/Feather.js
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/index.css
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/index.js
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/import-popper.js
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/PageDataOverview.js
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/index.html
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/Graph.js
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/import-jquery.js
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/PageDataAllocations.js
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/PageDataAddressSpace.js
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/import-bootstrap.js
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/Tabbed.js
cargo:rerun-if-changed=/data1/workspace/bytehound/server-core/../webui/src/PageDataConsole.js
1.22.19
v16.15.0
/data1/workspace/bytehound/webui/node_modules/.bin
Building...
Bundling...
Packaging & Optimizing...
✨ Built in 12.77s

dist/index.html                                  363 B    933ms
dist/index.988daa5b.js                     ⚠️  1.18 MB    9.56s
dist/feather-sprite.fd1db7f3.svg              38.59 KB    536ms
dist/index.0865fb53.css                      286.56 KB    201ms
dist/fontawesome-webfont.3981e506.eot        161.86 KB    244ms
dist/fontawesome-webfont.3981e506.eot        161.86 KB    429ms
dist/fontawesome-webfont.58488e7e.woff2       75.35 KB    173ms
dist/fontawesome-webfont.ed962b83.woff        95.73 KB    244ms
dist/fontawesome-webfont.0caf0c90.ttf        161.67 KB    429ms
dist/fontawesome-webfont.a9323ae9.svg         378.7 KB    916ms
bin path/data1/workspace/bytehound/webui/node_modules/.bin
--- stderr
thread 'main' panicked at 'Failed to build WebUI; child process exited with error code None!', server-core/build.rs:154:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[harlanc]

manually issue the following commands and crash :

./node_modules/.bin/parcel build src/index.html --dist-dir dist ✨ Built in 12.28s

dist/index.html                                  363 B    902ms
dist/index.988daa5b.js                     ⚠️  1.18 MB    9.56s
dist/feather-sprite.fd1db7f3.svg              38.59 KB    547ms
dist/index.0865fb53.css                      286.56 KB    825ms
dist/fontawesome-webfont.3981e506.eot        161.86 KB    253ms
dist/fontawesome-webfont.3981e506.eot        161.86 KB    101ms
dist/fontawesome-webfont.58488e7e.woff2       75.35 KB    805ms
dist/fontawesome-webfont.ed962b83.woff        95.73 KB    253ms
dist/fontawesome-webfont.0caf0c90.ttf        161.67 KB    102ms
dist/fontawesome-webfont.a9323ae9.svg         378.7 KB    886ms
Segmentation fault (core dumped)

[koute]

Is this on master or is this the 0.8.0 release?

[harlanc]

Both version have the same problem..

[harlanc]

@koute Could please tell me your node version? Thx

[lingege32]

I have the same issue. segmentation fault in index.xxx.js.

My node version is v16.14.2. bytehound version is 0.11.0.