-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Thread 'tokio-runtime-worker' panicked at 'Receiver::next_message called after None
'
#6871
Comments
From a first look substrate/primitives/consensus/common/src/import_queue/buffered_link.rs Lines 142 to 146 in 38a974c
I am not familiar enough with the code to judge whether it should be impossible that the receiver returns |
What is worrisome is that this can only happen if the block import task shuts down, and this shut down is not supposed to happen. |
To give some context about this code: the The The background task is designed to gracefully shut down if one of the channels is closed. Again, these channels are fields in the Consequently, the only ways this issue can happen is:
|
It could be that the process was shut down by the OOM killer. |
@arkpar no messages around that time, in general the memory usage looks pretty sane compared to the total memory of the node (16gb), you can see in the image attached the memory usage in the last 6 hours, with the crashes happening always below 2GiB |
We merged #6876, which doesn't fix the root of the problem but will change the error to a different one (that might be more useful) for the next time. |
A node running
v0.8.22
is eventually crashing with the error in the issue title, full log here https://paste.ubuntu.com/p/KNd7cHfRZ6/The text was updated successfully, but these errors were encountered: