elements: Crashes during initial block download without any error message

I tried both elementsd and elements-qt, and they both crashes repeatedly during initial blockchain sync. It seems that it always crashes when syncing the block data of December, 2018.

What’s more confusing, is that it always crashes without any error message in the “debug.log” output, the process simply disappears.

Actual behavior

After outputting last few logs like the following, the process simply crashes (exited?) and disappears:

2023-07-13T20:53:20Z UpdateTip: new best=dbe8f45c12614d436606da0e665db5414963da55ccfdc40cdf1a66c0d781e03b height=109668 version=0x20000000 tx=113110 date='2018-12-25T11:46:59Z' progress=0.044000 cache=0.0MiB(9txo)
2023-07-13T20:53:28Z UpdateTip: new best=e5d6e9d4a70955498796921fb88a2073df09cec6e596ff13dc76ad30bafec92d height=109669 version=0x20000000 tx=113111 date='2018-12-25T11:47:59Z' progress=0.044000 cache=0.0MiB(9txo)

Expected behavior

Do not crash.
When it does crash, at the very least, log the error message or the exceptions thrown so that we can know what went wrong.

To reproduce Download elements-core 22.1.1, and start syncing from the genesis block.

System information

elements-22.1.1-x86_64-linux-gnu.tar.gz from the GitHub release page

Ubuntu 22.04.1

Log of crashing and then I’m restarting elementsd:

=110012 version=0x20000000 tx=113455 date='2018-12-25T17:30:59Z' progress=0.044000 cache=0.0MiB(12txo)
2023-07-13T20:47:46Z UpdateTip: new best=bdb7a26f8342a7e93097b7c537f372571cedc37dea344d1be0d63822331a77ce height
=110013 version=0x20000000 tx=113456 date='2018-12-25T17:31:59Z' progress=0.044000 cache=0.0MiB(12txo)
2023-07-13T20:47:46Z UpdateTip: new best=5692fd6b88df1503774635b958f0292a1c02262082638e47ec4eb532cb87c66d height
=110014 version=0x20000000 tx=113457 date='2018-12-25T17:32:59Z' progress=0.044000 cache=0.0MiB(12txo)





2023-07-13T20:49:20Z Elements Core version v22.1.1 (release build)
2023-07-13T20:49:20Z Qt 5.12.11 (static), plugin=xcb (static)
2023-07-13T20:49:20Z Static plugins:
2023-07-13T20:49:20Z  QXcbIntegrationPlugin, version 330752
2023-07-13T20:49:20Z Style: fusion / QFusionStyle
2023-07-13T20:49:20Z System: Ubuntu 22.04.2 LTS, x86_64-little_endian-lp64

About this issue

Original URL
State: open
Created a year ago
Comments: 38 (15 by maintainers)

Most upvoted comments

FYI

When I stop elementsd for the 1st time after IBD completed, it moved all the 5.3g SWAP back to RES, which makes sense, because it’s doing FlushStateToDisk, and probably needed to access all those data in the memory:

2023-07-14T18:17:04Z Flushing block index, trimming headers, setTrimmableBlockIndex.size(): 4
2023-07-14T18:17:04Z FlushStateToDisk: write coins cache to disk (1173965 coins, 277647kB) starte
d
2023-07-14T18:18:13Z FlushStateToDisk: write coins cache to disk (1173965 coins, 277647kB) comple
ted (69.39s)
2023-07-14T18:18:13Z Flushing block index, trimming headers, setTrimmableBlockIndex.size(): 0
2023-07-14T18:18:13Z FlushStateToDisk: write coins cache to disk (0 coins, 14660kB) started
2023-07-14T18:18:13Z FlushStateToDisk: write coins cache to disk (0 coins, 14660kB) completed (0.
00s)
2023-07-14T18:20:00Z Shutdown: done

And, when I restart elementsd afterwards, now it only consumes 3.8g memory in total, consistent with the “3.7 gb estimation”.

BitcoinWukong on Jul 14, 2023

maybe just not enough swap? what does free say? 🤔

psgreco on Jul 14, 2023