New issue
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beacon node crash #12161
Labels
Comments
Thanks for this report. The most relevant part of your crash log is pasted below
Looks related to recent forkchoice changes. cc @potuz |
Concurrent map read/writes and this one seems to read without securing a read lock. prysm/beacon-chain/forkchoice/doubly-linked-tree/forkchoice.go Lines 259 to 263 in e2fa7d4
|
Wow that was taken care of super fast! Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃悶 Bug Report
Description
Beacon node crashed and restarted.
Version 3.2.2
Execution client is Erigon version 2.40.1-stable
Has this worked before in a previous version?
This was the first time it happened.
馃敩 Minimal Reproduction
No relevant flags other than
--execution-endpoint
of course.馃敟 Error
prysm_error.log
馃實 Your Environment
Operating System:
LXC running Ubuntu 22.04.1 LTS
What version of Prysm are you running? (Which release)
3.2.2
Anything else relevant (validator index / public key)?
The text was updated successfully, but these errors were encountered: