Closed aboimpinto closed 6 years ago
After +/- 390.000 blocks the system start to degrade and create more and more thread (reach a total of 41) and when reach 600.000 blocks processed the process was using 15G of memory
Something doesn't match
This method is consuming a lot of memory, is wrong, i will patch this
@aboimpinto Your tests was very helpful to find and fix this issue, thanks!
This is for sure a bug. The second param for Range is count. So it should be toHeight - fromHeight.
I left the sync run for some hours and the result is that is stuck in the Block 1.271.699. I already experience this happen when the block persistence try to persist the transactions. I don't know witch transaction is blowing up but it's a miner transaction or a claim transactions
The memory consummation is stable now but the number of the open thread is a little bit high at this point (22)
the nodes outputs
This is other bug, @aboimpinto the chain was synchronized without problems
The problem here was a memory issue.
Testing last Sync Algorithm deployed by @osmirnov on 21.10.2018