Open pinko-fowle opened 4 years ago
Probably start debugging by editing $HOME/.avn/bin/avn.sh
and commenting out parts of the script until it doesn't fork bomb any more. Could be specific to your config, but also could be a bug in the library. Let me know what you find.
Trying to change to a directory or run
__avn_debug
causes an infinite loop of processes to keep getting spawned. I am using zsh.chpwd_functions=( __avn_Chpwd )
. I can think of nothing I can do to make this any simpler. I have tried various .nvmrc configurations. I have tried repeating the install setups whilenvm use
'ing different nvms. I continue to get never ending fork bombs. I have not found any way to begin to get debugging information about what is causing this.Details
avn --version
: 0.2.4node --version
: v13.10.1nvm --version
: v0.35.3n --version
: none (i also tried homebrew install n, which was version 6.4.0, & got the same result)zsh --version
: 5.8bash --version
: 3.2.57The output of
__avn_debug
in the directory with a.node-version
file is:this fork bombs (endlessly spawns new proceses) my system with no output to the screen.
avn
is loaded in my~/.zshenv
file with:nvm specific
nvm
user I am confirming that I did not install with Homebrew