Skip to content
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

Closed
gabrielnergaard opened this issue Feb 21, 2019 · 8 comments · Fixed by #487
Closed

Corruption because of setBlockIndexCandidates.empty() assertion. #405

gabrielnergaard opened this issue Feb 21, 2019 · 8 comments · Fixed by #487
Labels
Component: Core App Related to the application itself. Dev Status: In Progress Someone is actively working on this issue. Priority: 3 - High Critical item that should be done as soon as possible Tag: Chainstate Related to blockindexes and the state of the chain. Tag: Segfault This issue causes the application to crash.
Milestone

Comments

@gabrielnergaard
Copy link
Contributor

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.

@presstab presstab added Dev Status: Help Wanted Seeking someone to help resolve this issue. Nobody is actively working on the issue. Component: Core App Related to the application itself. Tag: Segfault This issue causes the application to crash. labels Feb 21, 2019
@presstab presstab changed the title Bug — App crash on OS X Corruption because of setBlockIndexCandidates.empty() assertion. Feb 21, 2019
@presstab presstab added Tag: Chainstate Related to blockindexes and the state of the chain. Priority: 3 - High Critical item that should be done as soon as possible labels Feb 21, 2019
@presstab presstab added this to the v1.0.1 milestone Feb 21, 2019
@onezetty
Copy link

Same happened to me at Ubuntu 16.04

➜  bin veil-qt: validation.cpp:3265: void CChainState::PruneBlockIndexCandidates(): La declaración `!setBlockIndexCandidates.empty()' no se cumple.

[1]  + 15407 abort (core dumped)  ./veil-qt

@presstab
Copy link
Contributor

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.

@CryptoMaximalist
Copy link

CryptoMaximalist commented Feb 24, 2019

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

@Iconoclasta
Copy link

Iconoclasta commented Mar 1, 2019

Likewise, compiled from master @ #416 on ubuntu 16.04- user@ip:~$ ./veild veild: validation.cpp:3265: void CChainState::PruneBlockIndexCandidates(): Assertion `!setBlockIndexCandidates.empty()' failed. Aborted (core dumped)

@presstab presstab added Dev Status: In Progress Someone is actively working on this issue. and removed Dev Status: Help Wanted Seeking someone to help resolve this issue. Nobody is actively working on the issue. labels Mar 5, 2019
@presstab
Copy link
Contributor

presstab commented Mar 5, 2019

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 -reindex-chainstate

@Elysiumcore
Copy link

The same just happened to me. A simple shut down in Mac OS Mohave. Wallet will not restart. will have to resync chain

@veilgets
Copy link

Can this be closed? It's fixed.

@codeofalltrades
Copy link
Collaborator

Closing. Included in release v1.0.3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Core App Related to the application itself. Dev Status: In Progress Someone is actively working on this issue. Priority: 3 - High Critical item that should be done as soon as possible Tag: Chainstate Related to blockindexes and the state of the chain. Tag: Segfault This issue causes the application to crash.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants