We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Versions bcoin v1.0.2 (f57bd51 latest master branch) nodejs v9.9.0
Expected
A full node to completely sync and not over allocate memory.
Actual
A full node will over allocate memory during the initial sync:
[debug] (chain) Memory: rss=2504mb, js-heap=1368/1425mb native-heap=1079mb [info] (chain) Block 00000000000008079751b074b5c8c5e36e40880fa8884e5ba791586d1f0ffc63 (136400) added to chain (size=2326 txs=5 time=1.93599).
Here the memory is getting dangerously close to the max.
Reproduce
Switch to use nodejs v9.9.0:
nvm install v9.9.0
Alternatively use n v9.9.0 or another preferred method.
n v9.9.0
Start a fresh sync for mainnet:
./bin/bcoin
Watch the logs and see the js-heap grow in size until... you know the rest.
Resolution
Switch to nodejs v10, and start the sync again and watch the logs and see the js-heap does not keep growing in size.
Thanks to @tuxcanfly for identifying the issue.
The text was updated successfully, but these errors were encountered:
Closed by #903 as Node.js v9.9.0 is less than v10.
Sorry, something went wrong.
No branches or pull requests
Versions
bcoin v1.0.2 (f57bd51 latest master branch)
nodejs v9.9.0
Expected
A full node to completely sync and not over allocate memory.
Actual
A full node will over allocate memory during the initial sync:
Here the memory is getting dangerously close to the max.
Reproduce
Switch to use nodejs v9.9.0:
Alternatively use
n v9.9.0
or another preferred method.Start a fresh sync for mainnet:
Watch the logs and see the js-heap grow in size until... you know the rest.
Resolution
Switch to nodejs v10, and start the sync again and watch the logs and see the js-heap does not keep growing in size.
Thanks to @tuxcanfly for identifying the issue.
The text was updated successfully, but these errors were encountered: