-
Notifications
You must be signed in to change notification settings - Fork 92
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
Corruption because of setBlockIndexCandidates.empty() assertion. #405
Comments
Same happened to me at Ubuntu 16.04
|
I saw this once today, was not sure if it was from me switching between different branches... Will see if I can get it to happen again and save my datadirectory with the faulty state for testing. |
I have 2 data directories with this error now, one of which is my snapshot node. Both ubuntu 18.04 x64, neither ever self compiled, one brand new with the (apparently bad) snapshot. Let me know on discord if I can get these to you to help @presstab |
Likewise, compiled from master @ #416 on ubuntu 16.04- |
Seems to be an issue that causes the block indexes on load to have the number of tx's zeroed, then causing issues later in the loading process to arise because of it. Have not found a solution other than running with |
The same just happened to me. A simple shut down in Mac OS Mohave. Wallet will not restart. will have to resync chain |
Can this be closed? It's fixed. |
Closing. Included in release v1.0.3.0 |
Running OS X Mojave, wallet version 1.15, the app frequently gets into a state (twice this week) in which simply quitting and then trying to restart results in a crash. When this happens, the only solution is to start fresh from a snapshot.
From the OS X crash reporter, this is found:
Application Specific Information:
Assertion failed: (!setBlockIndexCandidates.empty()), function PruneBlockIndexCandidates, file validation.cpp, line 3265.
I haven't found a way to reproduce the error on demand. There have, however, been other reports of this in both the Veil internal support channel, and on the public side.
The text was updated successfully, but these errors were encountered: