You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a rayon-related deadlock in snarkOS, but I'm not quite sure which situation it actually is:
Using rayon parallel iterators while holding a Mutex or write RwLock (this case). See multiple discussions like this and this.
Using rayon with blocking calls (not sure if spawn_blocking applies here). Maybe see this or this.
I think it's probably the first one, as from a deadlock core dump, I did see write lock being acquired while the node stuck at a read lock. Here is the full backtrace of all threads. (Large text file as rayon tend to generate a deep stack. The file is actually .7z but has to be named .zip to upload here.) Notice the thread 69 has the write lock to vm.process while trying to advance a block, while there are many threads trying to validate incoming unconfirmed transactions and needed a read lock.
Steps to Reproduce
Not sure. Run the node with a large number of connections?
Expected Behavior
The node should not deadlock.
Your Environment
The text was updated successfully, but these errors were encountered:
馃悰 Bug Report
There is a rayon-related deadlock in snarkOS, but I'm not quite sure which situation it actually is:
spawn_blocking
applies here). Maybe see this or this.I think it's probably the first one, as from a deadlock core dump, I did see write lock being acquired while the node stuck at a read lock. Here is the full backtrace of all threads. (Large text file as rayon tend to generate a deep stack. The file is actually .7z but has to be named .zip to upload here.) Notice the thread 69 has the write lock to
vm.process
while trying to advance a block, while there are many threads trying to validate incoming unconfirmed transactions and needed a read lock.Steps to Reproduce
Not sure. Run the node with a large number of connections?
Expected Behavior
The node should not deadlock.
Your Environment
The text was updated successfully, but these errors were encountered: