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
For several minutes memory usage always increases until it causes OOM
stable - v4.0.1
Command : ./lighthouse bn --disable-upnp --network mainnet --execution-endpoint http://localhost:8551 --execution-jwt /home/ozard/nodes/prysm/jwt.hex --debug-level=info --metrics --validator-monitor-auto --suggested-fee-recipient 0x90D9bA78BdebE13B91426210E6F7e802A4E640fE --checkpoint-sync-url=https://beaconstate.info
Stable
Please describe the steps required to resolve this issue, if known.
The text was updated successfully, but these errors were encountered:
We are tracking this here (#4918) and working on a new release to fix it as a matter of high urgency.
Sorry, something went wrong.
In your screenshot, Lighthouse is only using 4.5GB of memory (the RES column), so maybe you have something else that contributes to the OOM as well.
No branches or pull requests
Description
For several minutes memory usage always increases until it causes OOM
Version
stable - v4.0.1
Present Behaviour
Command :
./lighthouse bn --disable-upnp --network mainnet --execution-endpoint http://localhost:8551 --execution-jwt /home/ozard/nodes/prysm/jwt.hex --debug-level=info --metrics --validator-monitor-auto --suggested-fee-recipient 0x90D9bA78BdebE13B91426210E6F7e802A4E640fE --checkpoint-sync-url=https://beaconstate.info
Expected Behaviour
Stable
Steps to resolve
Please describe the steps required to resolve this issue, if known.
The text was updated successfully, but these errors were encountered: