4.0.1.2 and 4.0.1.3 seemed to be working fine. I installed 4.0.1.4 and it just hangs, puts the cpu's at 100%. Tried rebooting and restarting, so far I haven't been able to get it to open.
Any suggestions for 4.0.1.4?
If you have a lot of mature coins, the CPU usage might be from staking coins. That will hang your computer. You wouldn't have been able to stake with 4.0.1.2 and 4.0.1.3.
If you believe that staking is not causing the sluggish behavior, please
- Stop your 4.0.1.4 client
- Dete the debug.log file in your roaming folder
- Restart your client and wait a while
- Paste the contents of your log file or PM us with a private link (google drive) if you'd like to keep the log private
It finally opened after close to an hour. Will close it tonight after work and try again to check the open time.
Notes on High CPU and Memory Usage
The high CPU usage you see when opening the wallet is most likely a result of loading and validating the block index. High CPU and memory usage is also expected when synchronizing the chain because each block must be validated by re-calculating the block hash and Merkle tree. These activities take considerable resources. Remember that this data structure was originally calculated by GPUs over the course of months.
Bear in mind that it takes 1 to 2 weeks to sync a BTC wallet from the genesis block. EBT may take 6 to 8 hours, which is very fast by comparison.
Synchronization may be faster (3-4 hours) with better connected nodes (nodes that have a dedicated IP, lots of peers, a public open port 3133, and fast internet speeds). In such cases, the CPU usage will be very high because synchronization speed is dependent largely on the computational burden of validating blocks.
For EBT, also expect high memory usage during and after synchronization. The block index is 180 MB and the block database is 166 MB. These large sizes are a consequence of the short block times (30 seconds). Short block times produce fast transactions and confirmations but the tradeoff is that they require computational resources to maintain. In return for expending these resources, EBT holders are awarded PoS interest if they keep their wallets open for minting.
We have tested the 4.0.1.4 wallets thoroughly and all resource usage has appeared normal. Several clients on both Mac and Windows have synchronized reasonably fast and with complete success. If your synchronization hangs for more than an hour, please delete your peers.dat and try the following nodes in your EBT.conf file:
addnode=192.211.62.50
addnode=114.22.28.17
addnode=95.43.216.142
addnode=68.35.89.205
addnode=50.125.168.242
If the synchronization still hangs (after the splash screen), you may have to resync the full chain.
You can also speed up synchronization by adding the following line into your EBT.conf file:
stake=0
This prevents the stake minting thread from starting. Once synchronized, you can quit the client, remove the line from EBT.conf, and restart the client. The block index will take from 2 minutes to 1 hour to load depending on your system. Expect high CPU and memory usage during this time.