-
Notifications
You must be signed in to change notification settings - Fork 490
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
state
: Concurrent Map Writes
#1174
Comments
Same issue here. In my case this also just happened around 00:16 UTC. It seems at the point of panicking, there are 2 goroutines that are related to
|
In fact this may not be as rare as we thought. After panic, when the node has synced to roughly the same height, it panicked again. However, the third sync attempt proceeded without issue. |
Same here. We had 3 separately nodes all panic at around 00:16 UTC as well. One of those panicked again at the same height, but made it past the second time. |
Thank you for informing, folks. We are having a look at this and will post a fix soon. |
Experienced this several times as well. I think it's related to #1006, and the block-stm code. I'm also doing a lot of tracing so not sure if thats related. |
That was amazingly fast. Thanks!! |
Also saw the issue here. |
We have noticed a rare race condition that results in either a concurrent write panic or a locked state on the main thread. This is reported as stemming from the following line:
bor/core/state/state_object.go
Line 173 in 241af1f
It happens infrequently and results in either a restart or the main thread no longer progressing.
Version:
v1.2.3
OS: Ubuntu 22.04
Start of error log:
The text was updated successfully, but these errors were encountered: