Locking issues #7584

martinschwarz commented at 9:52 PM on February 23, 2016: none

I am running 0.12.0 x86-64 as well as x86-32 on Windows 7. I'm experience significant locking issues while reindexing or rebuilding the blockchain. Basically, every ~10 seconds of processing, the window freezes for ~30s. Then the window unfreezes and processing continues for ~10s. These freezing intervals are also apparent in the time stamps in the log file. But other than the time gaps no errors are reported.

martinschwarz commented at 10:07 PM on February 23, 2016: none

Log file attached. Notice the time gaps 21:56:02 - 21:56:18 (16s freeze) 21:56:19 - 21:56:46 (27s freeze) 21:56:50 - 21:57:17 (27s freeze)

debug.log.txt

jonasschnelli added the label GUI on Feb 24, 2016

laanwj commented at 7:37 AM on February 24, 2016: member

Probably the same issue as: Bitcoin Core 0.10 freezing and disconnecting during synchronization #5851

jonasschnelli commented at 9:40 AM on February 24, 2016: contributor

What could be responsible for the time-freez (see below). The block is at height 4030 and has no transactions,... so it can't be the verification. Could it be FlushStateToDisk()? I guess LoadExternalBlockFile() can't be the reason.

2016-02-23 21:56:02 UpdateTip: new best=00000000c059ff0a3a8ee2f8a255c626fb370916c26c1119b6565771968c9c0d  height=4030  log2_work=43.976944  tx=4089  date=2009-02-12 18:57:15 progress=0.000017  cache=0.8MiB(3863tx)
2016-02-23 21:56:02 LoadExternalBlockFile: Processing out of order child 00000000f037ad09d0b05ee66b8c1da83030abaf909d2b1bf519c3c7d2cd3fdf of 00000000c059ff0a3a8ee2f8a255c626fb370916c26c1119b6565771968c9c0d
2016-02-23 21:56:18 UpdateTip: new best=00000000f037ad09d0b05ee66b8c1da83030abaf909d2b1bf519c3c7d2cd3fdf  height=4031  log2_work=43.977302  tx=4090  date=2009-02-12 18:58:42 progress=0.000017  cache=0.8MiB(3864tx)
2016-02-23 21:56:18 LoadExternalBlockFile: Processing out of order child 00000000ca4b69045a03d7b20624def97a5366418648d5005e82fd3b345d20d0 of 00000000f037ad09d0b05ee66b8c1da83030abaf909d2b1bf519c3c7d2cd3fdf
2016-02-23 21:56:18   nActualTimespan = 1401591  before bounds
2016-02-23 21:56:18 GetNextWorkRequired RETARGET
2016-02-23 21:56:18 params.nPowTargetTimespan = 1209600    nActualTimespan = 1401591
2016-02-23 21:56:18 Before: 1d00ffff  00000000ffff0000000000000000000000000000000000000000000000000000
2016-02-23 21:56:18 After:  1d00ffff  00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff
2016-02-23 21:56:18 UpdateTip: new best=00000000ca4b69045a03d7b20624def97a5366418648d5005e82fd3b345d20d0  height=4032  log2_work=43.97766  tx=4091  date=2009-02-12 19:16:30 progress=0.000017  cache=0.8MiB(3865tx)
2016-02-23 21:56:18 UpdateTip: new best=0000000027630bf5db66c00a0efbc93c9e1ad088286f9564a80f4987deb97c86  height=4033  log2_work=43.978017  tx=4092  date=2009-02-12 19:38:39 progress=0.000017  cache=0.8MiB(3866tx)
2016-02-23 21:56:18 LoadExternalBlockFile: Processing out of order child 0000000005974e0f9b1080c8a9bf635110ec84262c280ce91008ab4569449640 of 0000000027630bf5db66c00a0efbc93c9e1ad088286f9564a80f4987deb97c86
2016-02-23 21:56:18 Update

laanwj commented at 10:12 AM on February 24, 2016: member

Yes, strange, usually we see this later in the sync process (say, when catching up with a recent part of the chain). At lower heights the problem is usually not that bad yet.

martinschwarz commented at 8:03 AM on February 25, 2016: none

I was able to work around that issue using -disablewallet

fanquake closed this on Mar 6, 2018

MarcoFalke locked this on Sep 8, 2021