Assertion failure in mutex lock after issuing RPC stop command during sync

[BigBlockIfTrue]

I found this in my terminal after issuing a stop command:

bitcoind: /usr/include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.

The JSON-RPC stop command was issued over HTTP. At that time the node was in the process of syncing towards the chain tip. The error was printed to my terminal after the HTTP request completed successfully.

Apparently it still took some time after that until the node shut down (it did not crash immediately on the assertion failure), because my first attempt to start the node after the assertion failure failed with:

Error: Cannot obtain a lock on data directory [...]. Bitcoin Unlimited Cash Edition is probably already running.

Some time later I tried again and the node started without problems.

I use Cash Edition v1.6.0.0-unk, Linux x86_64, installed via Ubuntu repository.

[ptschip]

thanks for the report, there is a fix in the dev branch which will be released sometime early to mid next week.

…

On 11/07/2019 12:36 p.m., BigBlockIfTrue wrote: I found this in my terminal after issuing a |stop| command: |bitcoind: /usr/include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed. | The JSON-RPC |stop| command was issued over HTTP. At that time the node was in the process of syncing towards the chain tip. The error was printed to my terminal /after/ the HTTP request completed successfully. Apparently it still took some time after that until the node shut down (it did not crash immediately on the assertion failure), because my first attempt to start the node after the assertion failure failed with: |Error: Cannot obtain a lock on data directory [...]. Bitcoin Unlimited Cash Edition is probably already running. | Some time later I tried again and the node started without problems. I use Cash Edition v1.6.0.0-unk, Linux x86_64, installed via Ubuntu repository. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1843?email_source=notifications&email_token=ADCELUEY3WXPJ5ZGJQ7H7R3P66DTLA5CNFSM4IBSOO5KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G6W5TIQ>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADCELUAQP772EA4HPEYAKETP66DTLANCNFSM4IBSOO5A>.