Geth version: Geth/v1.7.0-unstable-03d00361/windows-amd64/go1.9
OS & Version: Windows 64-bit
Commit hash : 03d00361
Expected behaviour
I ran geth removedb followed by geth fast --cache=2048 console
I expected to sync the blockchain.
Actual behaviour
I ran geth removedb followed by geth fast --cache=2048 console
The blockchain correctly synced for 5-6 hours until block 4244028 (shown in log below) until geth dropped my peers and gave a fatal error: out of memory.
I then tried to run geth fast --cache=2048 console again and received the panic: runtime error: invalid memory address or nil pointer dereference error.
Steps to reproduce the behaviour
Run geth removedb followed by geth fast --cache=2048 console to perform a fast sync.
The backtrace below includes the logs when I ran both commands.
Looks like it is properly syncing again so I don't have a problem. Feel free to close unless you have more questions about what happened when it crashed. Hope the traces above help!
System information
Geth version: Geth/v1.7.0-unstable-03d00361/windows-amd64/go1.9 OS & Version: Windows 64-bit Commit hash : 03d00361
Expected behaviour
I ran
geth removedb
followed bygeth fast --cache=2048 console
I expected to sync the blockchain.
Actual behaviour
I ran
geth removedb
followed bygeth fast --cache=2048 console
The blockchain correctly synced for 5-6 hours until block 4244028 (shown in log below) until geth dropped my peers and gave a
fatal error: out of memory
.I then tried to run
geth fast --cache=2048 console
again and received thepanic: runtime error: invalid memory address or nil pointer dereference
error.Steps to reproduce the behaviour
Run
geth removedb
followed bygeth fast --cache=2048 console
to perform a fast sync.The backtrace below includes the logs when I ran both commands.
Backtrace
Initial
geth fast --cache=2048 console
command.Second
geth fast --cache=2048 console
command.