bitcoin: Crash: b-httpworker.2[2027] general protection fault

Crash while running Bitcoin Core-Qt with watch-only wallet, v0.20.0

No crash

Window disappeared completely

Open Bitcoin Core and let it run for days Do nothing Window suddenly disappeared after hours/days of uptime

System information

bitcoin-qt v0.20.0 binary downloaded from website, sha256sum bitcoin-qt fd6c2aa5904325083d40edbc0af4668b24a2cf2dbe256a6319648b579de36d2d (I verified it by downloading bitcoin-0.20.0-x86_64-linux-gnu.tar.gz again on another computer, binary sha256sum matches)

OS: Debian GNU/Linux 10 (buster) x86_64 Kernel: 5.6.0-0.bpo.2-amd64 CPU: AMD Ryzen 7 1700 (16) @ 3.000GHz HDD: mdadm RAID1 consisting of 2x 2TB drives, very good throughput

DE: MATE WM: Metacity (Marco) WM Theme: Menta Shell: bash 5.0.3

GUI dissapeared completely, so no traces there dmesg says: [Thu Jul 23 08:06:35 2020] traps: b-httpworker.2[2027] general protection fault ip:55c5648aa040 sp:7f36f9ff9190 error:0 in bitcoin-qt[55c564488000+1dee000] debug.log says nothing, look at timestamps comparing to dmesg:

2020-07-23T06:43:59Z Socks5() connect to vibsdpohu3atcimw.onion:8333 failed: host unreachable
2020-07-23T06:48:47Z UpdateTip: new best=00000000000000000002452497d3a72f18778c843af3a05c994b08b9f534621f height=640383 version=0x20000000 log2_work=92.138711 tx=551189631 date='2020-07-23T06:48:37Z' progress=1.000000 cache=116.7MiB(838970txo) warning='62 of last 100 blocks have unexpected version.'
2020-07-23T06:51:30Z Pre-allocating up to position 0xd00000 in rev02163.dat
2020-07-23T06:51:31Z UpdateTip: new best=0000000000000000000ee02285dafe68a0fc329a495fc853b0f325fead22f8cd height=640384 version=0x20800000 log2_work=92.138731 tx=551191584 date='2020-07-23T06:51:15Z' progress=1.000000 cache=116.8MiB(839933txo) warning='62 of last 100 blocks have unexpected version.'
2020-07-23T06:52:19Z [default wallet] Submitting wtx (edited for privacy) to mempool for relay
2020-07-23T06:52:19Z [default wallet] ResendWalletTransactions: resubmit 1 unconfirmed transactions
2020-07-23T06:55:39Z UpdateTip: new best=0000000000000000000680fcdd48c25550fe0f1110bb58d2f521e1f415d3407a height=640385 version=0x20c00000 log2_work=92.138751 tx=551193516 date='2020-07-23T06:55:03Z' progress=1.000000 cache=117.1MiB(842826txo) warning='62 of last 100 blocks have unexpected version.'
2020-07-23T06:59:26Z [default wallet] Submitting wtx (edited for privacy) to mempool for relay
2020-07-23T06:59:26Z [default wallet] ResendWalletTransactions: resubmit 1 unconfirmed transactions


[crash happened here on 2020-07-23T07:06:35Z)
Bitcoin Core started again:

2020-07-23T07:27:49Z Bitcoin Core version v0.20.0 (release build)
2020-07-23T07:27:49Z InitParameterInteraction: parameter interaction: -proxy set -> setting -upnp=0
2020-07-23T07:27:49Z InitParameterInteraction: parameter interaction: -proxy set -> setting -discover=0
2020-07-23T07:27:49Z Qt 5.9.8 (static), plugin=xcb (static)
2020-07-23T07:27:49Z System: Debian GNU/Linux 10 (buster), x86_64-little_endian-lp64
2020-07-23T07:27:49Z Screen: default 1280x1024, pixel ratio=1.0
2020-07-23T07:27:49Z Assuming ancestors of block 0000000000000000000f2adce67e49b0b6bdeb9de8b7c3d7e93b21e7fc1e819d have valid signatures.
2020-07-23T07:27:49Z Setting nMinimumChainWork=00000000000000000000000000000000000000000e1ab5ec9348e9f4b8eb8154
2020-07-23T07:27:49Z Using the 'shani(1way,2way)' SHA256 implementation
2020-07-23T07:27:49Z Using RdSeed as additional entropy source
2020-07-23T07:27:49Z Using RdRand as an additional entropy source
2020-07-23T07:27:49Z Default data directory /home/(edited for privacy)/.bitcoin
2020-07-23T07:27:49Z Using data directory /home/(edited for privacy)/BitcoinCore/Blockchain
2020-07-23T07:27:49Z Config file: /home/(edited for privacy)/BitcoinCore/Blockchain/bitcoin.conf
2020-07-23T07:27:49Z Config file arg: addresstype="p2sh-segwit"
2020-07-23T07:27:49Z Config file arg: alertnotify="curl -sI --connect-timeout 1 http://localhost:62602/alertnotify?%s"
2020-07-23T07:27:49Z Config file arg: bind="127.0.0.1"
2020-07-23T07:27:49Z Config file arg: dbcache="8192"
2020-07-23T07:27:49Z Config file arg: deprecatedrpc="signrawtransaction"
2020-07-23T07:27:49Z Config file arg: disablewallet="0"
2020-07-23T07:27:49Z Config file arg: listen="1"
2020-07-23T07:27:49Z Config file arg: maxmempool="1024"
2020-07-23T07:27:49Z Config file arg: maxorphantx="1000"
2020-07-23T07:27:49Z Config file arg: maxuploadtarget="25313"
2020-07-23T07:27:49Z Config file arg: mempoolexpiry="744"
2020-07-23T07:27:49Z Config file arg: onlynet="onion"
2020-07-23T07:27:49Z Config file arg: par="16"
2020-07-23T07:27:49Z Config file arg: proxy="127.0.0.1:9050"
2020-07-23T07:27:49Z Config file arg: rpcpassword=****
2020-07-23T07:27:49Z Config file arg: rpcuser=****
2020-07-23T07:27:49Z Config file arg: rpcworkqueue="32"
2020-07-23T07:27:49Z Config file arg: server="1"
2020-07-23T07:27:49Z Config file arg: testnet="0"
2020-07-23T07:27:49Z Config file arg: torpassword=****
2020-07-23T07:27:49Z Config file arg: txindex="1"
2020-07-23T07:27:49Z Config file arg: walletnotify="curl -sI --connect-timeout 1 http://localhost:62602/walletnotify?%s"
2020-07-23T07:27:49Z Config file arg: zmqpubrawblock="tcp://127.0.0.1:29000"
2020-07-23T07:27:49Z Config file arg: zmqpubrawtx="tcp://127.0.0.1:29000"
2020-07-23T07:27:49Z Command-line arg: datadir="/home/(edited for privacy)/BitcoinCore/Blockchain"
2020-07-23T07:27:49Z Using at most 125 automatic connections (1024 file descriptors available)
2020-07-23T07:27:49Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2020-07-23T07:27:49Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2020-07-23T07:27:49Z Script verification uses 15 additional threads
2020-07-23T07:27:49Z scheduler thread start
2020-07-23T07:27:49Z HTTP: creating work queue of depth 32
2020-07-23T07:27:49Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation.
2020-07-23T07:27:49Z HTTP: starting 4 worker threads
2020-07-23T07:27:49Z Using wallet directory /home/(edited for privacy)/BitcoinCore/Blockchain
2020-07-23T07:27:49Z init message: Verifying wallet(s) ...
2020-07-23T07:27:49Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2020-07-23T07:27:49Z Using wallet /home/(edited for privacy)/BitcoinCore/Blockchain
2020-07-23T07:27:49Z BerkeleyEnvironment::Open: LogDir=/home/(edited for privacy)/BitcoinCore/Blockchain/database ErrorFile=/home/(edited for privacy)/BitcoinCore/Blockchain/db.log
2020-07-23T07:27:49Z init message: Loading banlist ...
2020-07-23T07:27:49Z Using /16 prefix for IP bucketing
2020-07-23T07:27:49Z Cache configuration:
2020-07-23T07:27:49Z * Using 2.0 MiB for block index database
2020-07-23T07:27:49Z * Using 1023.8 MiB for transaction index database
2020-07-23T07:27:49Z * Using 8.0 MiB for chain state database
2020-07-23T07:27:49Z * Using 7158.2 MiB for in-memory UTXO set (plus up to 976.6 MiB of unused mempool space)
2020-07-23T07:27:49Z init message: Loading block index ...

I’ve edited few things (like tx and username of the machine) for privacy. Included debug.log just before crash (Bitcoin Core uses timestamp in GMT timezone looks like), then dmesg output (in my timezone which is GMT+1), and then debug.log output again from new start, so you can see my config and Core’s configuration. I am using Tor only network and I added extra threads and memory to Core, as I have plenty of computing power and RAM. Bitcoin Core can run for days or weeks, but today it crashed.

Hopefully it helps 😃 Thanks.