Re: [ANN][CROC] Official CrocodileCash Update Board [Strength in Basking]
After payment (withdrawal) ~ 1000 CROC, wallet freeze for ~5 minutes.
In debug.log I can see a lot of lines like this:
I don't know what process is this, and how to get rid of freezing?
In debug.log I can see a lot of lines like this:
Quote
WalletUpdateSpent found spent coin 1.00 TC 7788ee86901853ca9840a4ef5303db3e7a70cdbeea1684f20032d5b971213979
WalletUpdateSpent found spent coin 1.00 TC 77976a549f60e59b6212f656cef07d381e3ff3a7e6f94d694c7fec1d08c5ec49
WalletUpdateSpent found spent coin 1.00 TC 77a849586f232feacf455a412d3f5f809f217967a968ba22a2d3e91ec7891e92
WalletUpdateSpent found spent coin 1.00 TC 77b27889e51a5d93bc727f84800c483bcdeb84b01975661eae5dd930998af408
WalletUpdateSpent found spent coin 1.00 TC 77cbe271775807588fc9260feecf611a3118b720bfcae0d6bd9aa43fb5fcbc96
WalletUpdateSpent found spent coin 1.00 TC 77976a549f60e59b6212f656cef07d381e3ff3a7e6f94d694c7fec1d08c5ec49
WalletUpdateSpent found spent coin 1.00 TC 77a849586f232feacf455a412d3f5f809f217967a968ba22a2d3e91ec7891e92
WalletUpdateSpent found spent coin 1.00 TC 77b27889e51a5d93bc727f84800c483bcdeb84b01975661eae5dd930998af408
WalletUpdateSpent found spent coin 1.00 TC 77cbe271775807588fc9260feecf611a3118b720bfcae0d6bd9aa43fb5fcbc96
I don't know what process is this, and how to get rid of freezing?
At the source on Github I searched for WalletUpdateSpent and it returned two results (as shown here): https://github.com/RangaBoom/CrocodileCash/search?utf8=%E2%9C%93&q=WalletUpdateSpent&type=
It seems to be calling the function at line 345 of wallet.cpp (the other result is in the associated header file on line 179 of wallet.h). It appears to be calling this WalletUpdateSpent function and outputing/adjusting things for each CROC withdrawn -- at line 362. It takes some time to do this -- resulting in the freeze). Maybe lines 362-365 need to be streamlined or made more efficient somehow after more thorough investigation (obviously if line 362 is just a printline only that can be commented out -- but that won't free up too much of the time-lag).
Sorry my C/C++ is really rusty... (I can't remember for-instance what the "::" in the function call is [I think it had something to do with altering the scope of the function-call] and haven't investigated what the BOOST_FOREACH function is doing or where that subroutine/function is declared/spelled-out). it's a medium to long-term-goal for me to get reacquainted with this coding...
