0fd6ccef21
The cache is discarded when a block is popped, but then gets rebuilt when the difficulty for next block is requested. While this is all properly locked, it does not take into account the delay caused by a database transaction being only committed (and thus its effects made visible to other threads) later on, which means another thread could request difficulty between the pop and the commit, which would end up using stale database view to build the cache, but that cache would not be invalidated again when the transaction gets committed, which would cause the cache to not match the new database data. To fix this, we now keep track of when the cache is invalidated so we can invalidate it again upon database transaction commit to ensure it gets calculated again with fresh data next time it is nedeed. |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| blockchain.cpp | ||
| blockchain.h | ||
| blockchain_storage_boost_serialization.h | ||
| cryptonote_core.cpp | ||
| cryptonote_core.h | ||
| cryptonote_tx_utils.cpp | ||
| cryptonote_tx_utils.h | ||
| i_core_events.h | ||
| tx_pool.cpp | ||
| tx_pool.h | ||
| tx_sanity_check.cpp | ||
| tx_sanity_check.h | ||