Quote from: Tranz on July 30, 2017, 02:13:35 AM

Quote from: Zels on July 29, 2017, 11:47:30 PM

Quote from: Tranz on July 29, 2017, 06:04:57 PM

Version 1.5.5.0 is released.

https://github.com/Tranz5/HoboNickels/releases/tag/1.5.5.0

Please try this and give me your feedback regarding CPU usage.

Even worse than the 1.5.3 here.
Wallet use "only" 20% cpu, but can't do anything within the wallet. Wallet not responding for 2 - 3min each clic, he try to stake even when arrow is grey telling not stacking while acquiring node.

Back to 1.5.3 here Sad

I have not experienced this on any machine yet, more information would be helpful. Have you tried restart of the wallet? Can you also give me information about your system? Win Ver/CPU/RAM, how many wallets and How many blocks up for stake? Are you using S4C?

Just trying to get information for future improvements. Going forward the hard forks will be coded into 1.5.5+ so need to ensure it is working well for everyone. So a debug may help as well. Especially if you use the -debug startup switch and let it run for a bit.

You can also try to use the "Stop Staking" command in the wallet menu and see if that is helps, and then after the wallet is caught up and well connected try to start it back up.

Windows 7 SP1 Pro 64b
AMD Fx 6350 @ 3.9Ghz
16 GB ram

Only running 1 wallet on this machine, not using s4c.

2nd Try, started wallet 1.5.5, wait like 5min for wallet to get peer, about 5 - 6 peers and wallet is running fine, not lag at all.
I unlock my wallet with my passphrase and stacking start, wallet get laggy as hell ( My current weight is 1798991 soo many block ready to stack Grin

)
This wallet produce only orphan, with the 1.5.3 most of the block pass and mature with nearly the same weight

Tried using the new "Stop Staking" but he keep trying to stake or still laging and processing older transaction?

My launch parameter are D:\HoboNickels\HoboNickels-qt.exe -datadir=D:\HoboNickels -splitthreshold 50000 -combinethreshold 50000 -debug (normal to see 2017-07-30 12:56:47 splitthreshold set to 0 in debug log? )
Log sent to you in private. Hope it will help