-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Exception Syncing MainNet Chain from Block file #391
Comments
The block file I used was the full chain package from sync.ngd.network 2018/09/18 | 2742082 | 3.68G | 9h | download MD5:FBC140BAF08939935D7E0A51635F3B7B |
|
Hmm. it's happened again for me when loading a previous chain file I had used on block 2183574
Slightly different code path. |
This may be due to a change I made not present in current core code. I've backed out my local change and will close the issue if the problem clears up. |
Seems it was related to a change I was testing |
I spoke too soon; it still happened; just later along this time at block 2450457:
Going to have to dive deeper. |
Found one place where (outside of neo core code) where I was creating a chain Snapshot and failing to Dispose it; seems like an odd way to cause this if it is related, but trying syncing again with that fixed. |
Didn't fix it. Will look deeper at the end of the weekend. |
Interesting though; this last time it failed on the same key as previously, but at a much earlier block (1816512)
|
The issue was I wasn't referencing the latest neo-vm and reverting the commits that were merged in this PR (neo-project/neo-vm#52) were critical to proper operation. Hopefully if anyone else encounters the issue, the final finding here from this thread will be useful for them. |
I encountered the following exception while syncing the chain on MainNet using 2.9.0. It could have been hardware failure or something, but wanted to see if others have encountered it and discuss.
The exception was thrown in Blockchain.cs line 495:
Doesn't seem like it should ever happen.
Stacktrace:
The text was updated successfully, but these errors were encountered: