Skip to content

Potential Deadlock detected with cs_vSend cs_vRecvMsg #531

Open
@dimxy

Description

Received couple potential deadlock messages running komodod with DEBUG_LOCKORDER debugging macro on:
First issue originates in in MSG_BLOCK processing:

POTENTIAL DEADLOCK DETECTED
Previous lock order was:
 (1) pnode->cs_vSend  net.cpp:1629 (TRY)
 cs_main  main.cpp:8649 (TRY)
 cs_wallet  wallet/wallet.cpp:3222
 (2) cs_mapRelay  net.cpp:1924
Current lock order is:
 pnode->cs_vRecvMsg  net.cpp:1610 (TRY)
 cs_main  main.cpp:7355
 (2) cs_mapRelay  main.cpp:7449
 (1) cs_vSend  net.cpp:2218
Assertion failed: (onlyMaybeDeadlock), function potential_deadlock_detected, file sync.cpp, line 127.

For the first issue there is a discussion and a fix in another repo: dimxy#71

The second issue is supposedly in "getheaders" processing:

POTENTIAL DEADLOCK DETECTED
Previous lock order was:
 pnode->cs_vRecvMsg  net.cpp:1590 (TRY)
 (1) cs_main  main.cpp:8080
 (2) cs_vSend  net.cpp:2198
Current lock order is:
 (2) pnode->cs_vSend  net.cpp:1609 (TRY)
 (1) cs_main  main.cpp:8710 (TRY)
 (1) cs_main  main.cpp:2551

The second issue is still being investigated.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions