-
Notifications
You must be signed in to change notification settings - Fork 20.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to perform copydb (panic: runtime error: memory) #15858
Comments
Possibly the same as #15796 |
I stumbled upon #15797 too and tried to get geth to "fast sync" with itself. It seems to have caused the same problem here. In my case it crashed around block 4253696 the first time. I happened to run the command with more cache (1024) than the OP. I also ran the command a second time with 2048 cache and it just crashed much faster around block 1048576, so that doesn't seem to make any difference. The contents of geth version output:
OS: Windows 10 Pro End of the output when using 1024 cache:
End of the output when using 2048 cache:
Crash using 4096 cache:
|
Ran into the same, maybe. Not mem-related, it's that the dropPeerFn is not set (nil) in the copydb initialization. I'll take a look tomorrow if it's the same, it's trivial to fix if so |
Yup, line 859:
However, |
… function is set (ethereum#15992)
… function is set (ethereum#15992)
System information
Geth version:
Geth/v1.7.3-stable-4bb3c89d/linux-amd64/go1.9
OS & Version: Ubuntu 16.04.3 x64
I was following @karalabe 's instructions in #15797 and I got to block number 2433095 when geth crashed:
Command I ran
geth --datadir=/gethswap copydb --cache=512 /geth/.ethereum/geth/chaindata
The text was updated successfully, but these errors were encountered: