How much memory does you machine have? We have seen this issue when the VPS has less than 512M available. There are a couple processes (with masternodes only), that spike the memory briefly, then it returns to normal. Are you running a masternode?
2015-09-25 17:05:55 mnw - invalid message - Masternode not in the top 10 (11)
2015-09-25 17:05:55 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (11)
2015-09-25 17:05:55 mnw - invalid message - Masternode not in the top 10 (11)
2015-09-25 17:05:56 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (13)
2015-09-25 17:05:56 mnw - invalid message - Masternode not in the top 10 (13)
2015-09-25 17:05:57 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (11)
2015-09-25 17:05:57 mnw - invalid message - Masternode not in the top 10 (11)
2015-09-25 17:05:57 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (11)
2015-09-25 17:05:57 mnw - invalid message - Masternode not in the top 10 (11)
2015-09-25 17:05:57 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (12)
2015-09-25 17:05:57 mnw - invalid message - Masternode not in the top 10 (12)
2015-09-25 17:05:57 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (11)
2015-09-25 17:05:57 mnw - invalid message - Masternode not in the top 10 (11)
2015-09-25 17:05:58 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (11)
2015-09-25 17:05:58 mnw - invalid message - Masternode not in the top 10 (11)
2015-09-25 17:05:58 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (11)
2015-09-25 17:05:58 mnw - invalid message - Masternode not in the top 10 (11)
2015-09-25 17:05:58 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (11)
2015-09-25 17:05:58 mnw - invalid message - Masternode not in the top 10 (11)
2015-09-25 17:05:59 CMasternodePaymentWinner::IsValid - Masternode not in the top 10 (12)
2015-09-25 17:05:59 mnw - invalid message - Masternode not in the top 10 (12)
0.12.0.45 had a memory leak, please update to latest version (0.12.0.53)Code:Out of memory: Kill process 22672 (dashd) score 710 or sacrifice child Killed process 22672 (dashd) total-vm:8553416kB, anon-rss:6572092kB, file-rss:0kB
I can give more details to developers of dash daemon.
Dash Core Daemon version v0.12.0.45-b2b2cef
It should level out at ~350M after some time - at least that's what I see on many of my processesThanks. Downloaded and started.
After start it takes 4-5Gb RAM, why?
All other wallets use less than 1Gb.