...
I have already tried going back to block 205xxx (the last snapshot I have) and start slimcoin connecting only to the block explorer with -listen=0. Will try out BitcoinFX's new node now. What I don't have done still is revising the peer list in slimcoin.conf for bad nodes, will do this too and then tell you if I had success.
I'm not sure the cause of this, but if it's a problem with handling orphan blocks then that's not good. Can't have users getting stuck on random points of the blockchain...
Agree, the client is WAY more stable now that some months ago, but this bug is really annoying.
Node is running v.0.3.2.1-alpha on win server. I also used the snapshot from slimcoin.club and got fully synced in under 3 hours, without adding / changing any .conf settings.
Try syncing with a fresh wallet.dat and then replacing it with your main wallet once synced, if your not already doing that. Anyway this new node seems to be very stable and the provider seems to have a good and fast network upstream. Number of connections is > 20 currently.
I will try to compiled and run a new windows version when we know its stable.
Cheers!