Analyze memory usage, look for memory leaks
Summary
Many people experience weird behaviour of Crown wallet and MN/SN nodes like stuck on a specific block, hanging, crashes, some of them produce this error:
************************
EXCEPTION: St9bad_alloc
std::bad_alloc
crown in ProcessMessages()Steps to reproduce
No actual steps to reproduce
Expected behavior
Wallets and nodes run without problems, though if it's proved that 1 GB of RAM is not enough we might need to raise hardware requirements.
Problematic behavior
Crashes, hanging, stuck on a specific block
Crown-core environment info
Ubuntu 16.04, Windows 10x64
Crown-core application info
v0.12.5.0, v0.12.5.1
Relevant logs and/or screenshots
Usually the last messages when a node is stuck are about reserving memory for the keypool:
2018-08-09 13:13:57 keypool reserve 2
2018-08-09 13:13:57 keypool return 2Possible fixes
- Analyze current memory usage
- Look for possible memory leaks
Monitoring Solutions
- https://www.digitalocean.com/community/tutorials/how-to-install-and-use-graphite-on-an-ubuntu-14-04-server
- sudo apt-get install htop
- https://cacti.net/
- Maybe Fabian can add 1 or 2?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information