Segmentation Fault when checking for update #997
Description
🐛 Bug description
Nothing actually bad happens, but when I try to run wasm-pack --help, the help message is printed, followed by Segmentation fault (core dumped).
$ wasm-pack help
wasm-pack 0.9.1
Ashley Williams <ashley666ashley@gmail.com>
📦 ✨ pack and publish your wasm!
USAGE:
wasm-pack [FLAGS] [OPTIONS] <SUBCOMMAND>
FLAGS:
-h, --help Prints help information
-q, --quiet No output printed to stdout
-V, --version Prints version information
-v, --verbose Log verbosity is based off the number of v used
OPTIONS:
--log-level <log_level> The maximum level of messages that should be logged by wasm-pack. [possible values:
info, warn, error] [default: info]
SUBCOMMANDS:
build 🏗️ build your npm package!
help Prints this message or the help of the given subcommand(s)
login 👤 Add an npm registry user account! (aliases: adduser, add-user)
new 🐑 create a new project with a template
pack 🍱 create a tar of your npm package but don't publish!
publish 🎆 pack up your npm package and publish!
test 👩🔬 test your wasm!
Segmentation fault (core dumped)
🤔 Expected Behavior
Help message should print, and program should exit.
👟 Steps to reproduce
I'm going to try to reproduce it by building it from source and running with valgrind. I will update this section once I have that information.
I'm not doing anything special besides running wasm-pack help or wasm-pack --help. The segfault is not deterministic, but it seems like it happens more often than not (might be confirmation bias though). I will try to get stats on this.
UPDATE: posted below
🌍 Your environment
Include the relevant details of your environment.
wasm-pack version: wasm-pack 0.9.1
rustc version: rustc 1.51.0 (2fd73fabe 2021-03-23)