I believe it is because the CPU usage is over xx% for a x minutes and the server operator kills the instance.
I don't think so because VULTR don't do this, I'm even mining of the VPS on VULTR and I'm using 100% of the cpu without problem.
And even on VULTR my daemon crash.
, just saw a .46 on dashninja
I really hope we get updates, I restarted every node at least 5 times in 2 days (and I didn't get any dash yet since upgrade...) or I'll have to evaluate to quit
256MB with no swap available seems to be too small for me to perform a reindex.
The best I can do is 30 to 50 percent progress and dashd crashes every time the daemon hits 95 percent ram usage. I've been playing around with ulimit, trying to find a variable that might actually limit dashd's memory usage temporarily so it can perform a successful reindex. No luck so far.
Verifying mncache.dat format...
.45 network subroutine had a bug which caused high resources locking errors,Is .46 up and running or still testing? I might wait some more days if we'll have .47+
On the other side, it's 50% less CPU, but i never crashed due to CPU spikes. I assume it's something else; whoever upgraded to .46 noticed a different behaviour?