client 0.18.0 crashes when computer wakes up from hibernation

weedcoder commented at 10:43 am on May 15, 2019: none

When my computer (Lenovo T470) wakes up from hibernation, during chain synchronization, bitcoin 0.18.0 crashes The expected behavior is not to crash and continue the synchronization.

The bitcoin client crashes

To reproduce, you have to have a syncing client, then put you computer to hibernation, then wake it up, it will crash.

I use the 0.18.0 version installed from ubuntu repository.

My laptop is a Lenovo T470 with ubuntu 18.10

the debug.log :

`2019-05-14T21:41:36Z UpdateTip: new best=0000000000000000001ba2346810a08a14e0b64e076afc13af0cdbf9997cffd7 height=574923 version=0x20c00000 log2_work=90.612962 tx=410552514 date=‘2019-05-07T02:50:05Z’ progress=0.993998 cache=346.3MiB(2599655txo) 2019-05-14T21:41:36Z

EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_15condition_errorEEEEE
boost::condition_variable::do_wait_until failed in pthread_cond_timedwait: Argument invalide
bitcoin in scheduler`

fanquake added the label Linux/Unix on May 15, 2019

MarcoFalke commented at 11:34 am on May 15, 2019: member

FWIW, I also hit this exception

fanquake commented at 11:36 am on May 15, 2019: member

Looks like the same exception as #14200.

weedcoder commented at 12:41 pm on May 16, 2019: none

This problem doens’t exist when the chain is synchronized.

fanquake commented at 9:28 am on May 20, 2019: member

I’ve just seen something similar to this/#14200. Running a self compiled v0.18.0 on macOS:

 02019-05-20T09:16:11Z IsBerkeleyBtree: No such file or directory /Users/michael/Library/Application Support/Bitcoin/indexes/wallet.dat
 12019-05-20T09:16:11Z IsBerkeleyBtree: No such file or directory /Users/michael/Library/Application Support/Bitcoin/indexes/txindex/wallet.dat
 22019-05-20T09:16:11Z UpdateTip: new best=00000000000000000001f2c8d9feb8544c7678d74cdab30a7ae16f4f361ce21a height=576297 version=0x20000000 log2_work=90.64279 tx=413922980 date='2019-05-16T12:01:00Z' progress=0.997020 cache=19.4MiB(145802txo)
 32019-05-20T09:16:12Z UpdateTip: new best=00000000000000000012f36b8a0f3e43a1f3bdc0e452e085ead071c0de663e0c height=576298 version=0x20000000 log2_work=90.642811 tx=413924878 date='2019-05-16T12:03:24Z' progress=0.997021 cache=20.2MiB(152064txo)
 42019-05-20T09:16:13Z UpdateTip: new best=00000000000000000015161d9def3e63c1907e8804d13c9c55d3a7886b59b3c3 height=576299 version=0x20000000 log2_work=90.642833 tx=413927861 date='2019-05-16T12:25:50Z' progress=0.997033 cache=21.0MiB(159346txo)
 52019-05-20T09:16:14Z UpdateTip: new best=0000000000000000002394c1e3c0d81c7c9c63920c77fbb4484e9dc02352137b height=576300 version=0x2000e000 log2_work=90.642854 tx=413930977 date='2019-05-16T12:28:52Z' progress=0.997035 cache=21.9MiB(166320txo)
 62019-05-20T09:16:14Z [default wallet] Releasing wallet
 72019-05-20T09:16:14Z Pre-allocating up to position 0xb00000 in rev01640.dat
 82019-05-20T09:16:14Z UpdateTip: new best=000000000000000000181dc5e64237d3394afa8163d0c1d29184b4e52e6f567c height=576301 version=0x20000000 log2_work=90.642876 tx=413934113 date='2019-05-16T12:39:48Z' progress=0.997040 cache=22.7MiB(173339txo)
 92019-05-20T09:16:14Z New outbound peer connected: version: 70015, blocks=576912, peer=2
102019-05-20T09:16:14Z Pre-allocating up to position 0x6000000 in blk01640.dat
112019-05-20T09:16:15Z UpdateTip: new best=00000000000000000007af1fa44f3ce1f3afc4407b08076c44536396954c1766 height=576302 version=0x20000000 log2_work=90.642897 tx=413936803 date='2019-05-16T12:41:49Z' progress=0.997042 cache=23.7MiB(180794txo)
122019-05-20T09:16:16Z UpdateTip: new best=000000000000000000033acc17d6a30317c0ef56a47fd398d67eefe4bc16cf58 height=576303 version=0x20c00000 log2_work=90.642919 tx=413939413 date='2019-05-16T12:59:49Z' progress=0.997051 cache=24.6MiB(188220txo)
132019-05-20T09:16:16Z 
14
15************************
16EXCEPTION: NSt3__112system_errorE       
17recursive_mutex lock failed: Invalid argument       
18bitcoin in scheduler       
19
202019-05-20T09:16:31Z

MarcoFalke commented at 10:47 am on May 20, 2019: member

@fanquake Was it also after hibernation?

fanquake commented at 1:47 pm on May 20, 2019: member

@MarcoFalke No. This happened very shortly after starting a node that was already ~98/99% synced.

MarcoFalke commented at 4:52 pm on June 27, 2019: member

Could you get the backtrace and the arguments that were passed to all methods in the backtrace?

Edit: The original comment was about

boost::condition_variable::do_wait_until failed in pthread_cond_timedwait: Argument invalide

The last comment is about

recursive_mutex lock failed: Invalid argument

fanquake commented at 5:17 am on June 29, 2019: member

I’ve moved my issue into #16307, and have removed the comments here.

elichai commented at 2:17 pm on October 13, 2019: contributor

Also happens with 0.19, archlinux. I think I’m using suspend though, not hibernation (if it makes any difference)

0************************                                                                                                                                                                                                                                
1EXCEPTION: N5boost10wrapexceptINS_15condition_errorEEE                                                                                                                                                                                                  
2boost::condition_variable::do_wait_until failed in pthread_cond_timedwait: Invalid argument                                 
3bitcoin in scheduler                                                                                                                                                                                                                                    
4                                                                                                                            
5terminate called after throwing an instance of 'boost::wrapexcept<boost::condition_error>'                                                                                                                                                              
6  what():  boost::condition_variable::do_wait_until failed in pthread_cond_timedwait: Invalid argument

debug.log https://termbin.com/u63c

MarcoFalke commented at 2:19 pm on October 13, 2019: member

We should probably replace boost with c++11 instead of trying to fix this issue

MarcoFalke commented at 8:54 pm on March 5, 2020: member

Still happens:

0[15:50] <sipa> MarcoFalke: it seems my bitcoind (commit a71c34742) died with boost::condition_variable::do_wait_until failed in pthread_cond_timedwait: Invalid argument  in debug.log

laanwj closed this on Mar 6, 2020

PastaPastaPasta referenced this in commit 417099870a on Sep 28, 2021

PastaPastaPasta referenced this in commit 9b8884b430 on Sep 28, 2021

kittywhiskers referenced this in commit efb9cdad7a on Oct 12, 2021

DrahtBot locked this on Feb 15, 2022

gades referenced this in commit 65ec4496fb on May 2, 2022

Munkybooty referenced this in commit 308aa902f3 on Nov 8, 2022

Munkybooty referenced this in commit 229a901ad8 on Nov 15, 2022

Munkybooty referenced this in commit 0b453d5296 on Nov 25, 2022

Munkybooty referenced this in commit e08534c56e on Nov 25, 2022

client 0.18.0 crashes when computer wakes up from hibernation #16027