This is just a FYI that an assert has been triggered on a release build of bitcoin core 22 by a user (not me): https://www.reddit.com/r/BitcoinBeginners/comments/zgykrj/my_second_attempt_at_setting_up_a_bitcoin_node/ This seems to be the assert that is now at chain.cpp:116, added 7 years ago. Hopefully this can hint someone of a scenario where it occurs to avoid crashing the process in the future?
-
bartoli commented at 8:20 PM on December 9, 2022: none
- bartoli added the label Bug on Dec 9, 2022
-
ghost commented at 10:19 PM on December 9, 2022: none
This seems to be the assert that is now at chain.cpp:116, added 7 years ago.
Its at Line 112:
https://github.com/bitcoin/bitcoin/blob/9e229a542ff2107be43eff2e4b992841367f0366/src/chain.cpp#L112
I am not sure how to reproduce this error however removing
assertand checking if the previous block exists before trying to access it should fix the error. -
maflcko commented at 10:49 AM on December 10, 2022: member
Bitcoin Core makes heavy use of CPU, RAM and disk IO. Hardware defects might only become visible when running Bitcoin Core. You might want to check your hardware for defects.
- memtest86 to check your RAM
- to check the CPU behaviour under load, use linpack or Prime95
- to test your storage device use smartctl or CrystalDiskInfo
- maflcko closed this on Dec 10, 2022
- maflcko added the label Data corruption on Dec 10, 2022
- maflcko removed the label Bug on Dec 10, 2022
- maflcko added the label Block storage on Dec 10, 2022
- bitcoin locked this on Dec 10, 2023
